I'd like to just use one language and hit all platforms.
You don't need a server-side language if the app doesn't really need to communicate with your server. You can do everything client-side with LocalStorage (SQLite) and cached assets. If the page has the right metadata on it, "Add to Home Screen" saves the whole app locally.
And there's no reason why the server, if it needs to exist, shouldn't be executing the same language (see http://nodejs.org/)
The modern web is the platform. There are nice local platforms, but your "write once run anywhere" 'native' app isn't going to fit in on any platform that actually gets used.
I think we're really choking ourselves as hackers if we let Browsers either end up as completely JS or the hacked together combination of (poorly enforced) HTML, (ugly syntax) CSS, and Javascript
You can argue this is not a good thing, as Cory Doctorow has at least tried to, but the argument comes across as tired and pointless. It's the ramblings of an "old man" (measured in internet years of course) who, had he been born a hundred years ago, would probably have been railing against car companies for removing the hand-start crank.
People don't want computers. They don't want notebooks. They don't want compilers or user serviceable parts.
What they do want is Facebook, YouTube, Twitter, and all the other things you can only do, for the most part, with computers and notebooks. The sooner some device delivers an alternative that's easier to use, more reliable, and less fuss in the long run, the sooner people will switch to that new thing.