You're completely right. I don't understand why everyone thinks we need to standardize on the web browser as the one true computing platform either. The sheer overhead involved is so upsetting when you see simple canvas/etc. demos that just chug when running on incredibly powerful computers and see people applauding the effort. Native compilation is too sweet a prize to give up; -webkit-box-shadow, the fucked box model, <video>, <canvas>, and friends are no substitute for a real, efficient software stack that isn't incredibly bloated and underperforming. The sooner HN at large realizes this, the sooner it can get to working on things that are actually new and interesting.
The only reason the web is considered the end-all-be-all is because people want to reach "average users" who can't handle installing native software and don't want the inconvenience of maintaining their computers' software. They never will, but that doesn't mean that the future of computing should be decided by the least common denominator of end-users.
The current trend in "web technologies" is to implement a wrapper for every native technology. When we finally finish, we'll end up with what can't possibly work better than what we had before, and it'll have taken incredible amounts of effort for programmers to optimize it enough that it's even usable for real jobs (see javascript engines at large). If all that programmers want is a standard software interface, they should construct one, but the browser as an environment has too much cruft from its history as a /content navigation tool/ to be an effective programming environment.
The only reason the web is considered the end-all-be-all is because people want to reach "average users" who can't handle installing native software and don't want the inconvenience of maintaining their computers' software. They never will, but that doesn't mean that the future of computing should be decided by the least common denominator of end-users.
The current trend in "web technologies" is to implement a wrapper for every native technology. When we finally finish, we'll end up with what can't possibly work better than what we had before, and it'll have taken incredible amounts of effort for programmers to optimize it enough that it's even usable for real jobs (see javascript engines at large). If all that programmers want is a standard software interface, they should construct one, but the browser as an environment has too much cruft from its history as a /content navigation tool/ to be an effective programming environment.