Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I feel like that's an old way of thinking. If websites are too grow up and become first class applications, and advancements in Chrome and Firefox are paving that way, we want the browser to become a very thin runtime that doesn't impose any behaviors of its own. It should be mostly transparent to the user that they are in a browser. The fact that different browsers use different shortcuts makes that all the more important, that browser shortcuts need to be invoked in other ways that won't conflict.


Split the web. If you want an applications platform with HTTP transport, build one. If you want a documents platform, build that as well.

Split out commerce and media while you're at it.

The present model's working increasingly poorly for me.


> It should be mostly transparent to the user that they are in a browser.

Even if the browser is providing your entire desktop experience, you should be able to switch applications or close them in a predictable way.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: