One one hand I'm happy to see the web able to do more and more. On the other hand, I worry that as we turn the browser into a platform with all these client side capabilities, browsers will become big complicated messes.
I wish we would see more browser features (cross-browser standards, app deployment style, ability to run random 3rd party code relatively securely, app interoperability) moved into the OS, rather than more OS features moved into the browser.
I can't quite yet make a native, cross-OS app I can deploy by clicking a link and that anyone will trust not to eat their computer just by running it. It's also a lot more work to implement things like networking.
Only nobody likes Java desktop applications. Including me, and I've programmed professionally in the language since 1998.
And they are non starters for demanding multimedia work, which is some of the most interesting stuff you want to do in the desktop as opposed as a web app.
.NET feels better (because MS didn't screw up as much, as Java did with the overengineered uncanny valley mess that is Swing), but it's not cross platform.
So, still, not comparable to deploying in the browser sandbox.
> So, still, not comparable to deploying in the browser sandbox.
That much is true, I haven't yet used so brain damaged set of programming tools as the HTML/JavaScript/CSS gimmick required to make the so called web applications in all browser versions required by our customers.
At least you have the chance to debug everywhere. Current native tools often are just fundamentally incompatible. Even if we just had hacky cross-os standards that'd be better than nothing.