[1] http://bethesignal.org/wp-content/uploads/2009/06/css-is-awe...
It gets better with some of the CSS3 layouts which more closely mirror what's ben available in the desktop world for ages, but using those is just a recipe for »Your site looks like crap on my browser« mails because they're not standardised yet or not yet widely-implemented (or your target audience uses something else than the bleeding-edge version).
I think the problem is the youth of today doesn't know anything other than web development, so they are full of false assumptions.
I wasn't implying desktop designers hard code everything -- but in fact many of them do or make assumptions that the app will NEVER be used on anything smaller than even the absurdly small 800x600. We're talking about mobile apps, responsiveness, the cost/benefit of targetting multiple devices with one app vs six native apps.
If you target multiple platforms with one app, you get an app that works from OK to poorly on lots of platforms. Look at Light Table as an example: done entirely via web technologies, easy to port everywhere, but feels incredibly alien and _wrong_ on my Mac. (No offense Chris!)
Compare to Sublime Text 2, which to my understanding has lots of platform-specific code to make it feel native on each platform, but also a shared core (using Cairo, etc). So "six native apps" need not cost anywhere near six times a single native app.
So in the end, the cost of targeting multiple platforms with a single app is surely lower than targeting each platform individually, but that's just a classic cost/quality tradeoff - the web limits your polish. And what good is having your app on multiple platforms if it's inferior to native alternatives on all of them? I know as a Mac user, I'll pick the Mac app that feels like a Mac app every time.
I don't know if responsive design is "hard" or not, but I observe that on the web, fixed widths are still incredibly common, and even major sites break easily. I visit Google, and if my window size is not at least one thousand pixels, the Sign In button is clipped and not initially visible. This would simply be considered a bug in a desktop app.
Besides, I always thought that layout was one of the weakest parts of HTML and CSS - witness the endless parade of hacks to achieve equal height columns.