I'm pretty sure I recall the same concessions being made for Swing when Java was up and coming.

(Of course, the difference here is that this is actually happening, but still...)

Another difference is UI startup time. The Java VM took minutes on most computers to go from URI entry to first UI display. Compare that to optimistic rendering all browsers do today, where delay is mostly dependant on network speed.

Tell that to anyone who uses their PC for programming, document creation, graphics design, or is comfortable with the command line.

I have been using webapps for said tasks more and more. Many tasks performed using a webapp do not yet have compelling advantages. But soon they will get them, I think. To name a bold example, http://C9.io: Not yet bringing many compelling advantages, but the tipping point is close.

Different strokes for different folks, I guess. I can't stand using a webapp for something that should be a desktop app. I just don't get the responsiveness I need. It's like using Photoshop without a mouse.

I had that experience a few years ago, when javascript execution engines where not optimized yet for speed. Today, I have the same experience with apps built using flash, where there is an annoying delay when hovering/clicking. A mature webapp running on a fast javascript engine does not give me any noticable delay. The "feel" is just the same as a native app.

c9 has one big advantage - before I was granted admin privileges at work, it allowed me to get started with some node work without having to install anything.

Thanks for reminding me of half of my html5 "todo" list.

[edit] whether I find the free time to get around to any of it is another matter, admittedly.