Re:Ask HN: What would you want in an ideal web browser?
by krapp on Monday August 17, 2015 @02:18PM
(#10075008)
I can imagine an "application browser" being essentially a virtualized runtime browser - you point to the 'url' of an application, it downloads the runtime and source code and environment (if you don't already have it) and everything gets sandboxed and compiled on the fly, and runs as if it were native code. Of course, nothing would touch your actual filesystem, and you could get rid of an application as easily as you clean your browser cache today. This would also have the advantage of being language agnostic.
This is already technically kind of sort of possible with any number of sites that use compile-to-js languages, but these are invariably limited by the capabilities javascript and HTML. I suppose the ultimate version of this would look like browseable software images like Docker or something.
Re:Ask HN: What would you want in an ideal web browser?
by barnacs on Monday August 17, 2015 @06:27AM
(#10072185)
Reader browser: I would argue that it should be a reader/writer browser, where authoring, changing and interlinking documents is just as trivial as browsing them.
Application browser: but then why limit it to JavaScript?
Re:Ask HN: What would you want in an ideal web browser?
by mod50ack on Monday August 17, 2015 @02:40PM
(#10075171)
I agree with the r/w web, and that was the original vision, but it's not really practical at this point because nobody supports such editing in a standard fashion
Re:Ask HN: What would you want in an ideal web browser?
by panic on Monday August 17, 2015 @06:03AM
(#10072124)
Chrome has support for "Chrome Apps" (https://developer.chrome.com/apps/about_apps) which make it at least partly an "application browser" as you're describing.
Re:Ask HN: What would you want in an ideal web browser?
by nekkoru on Monday August 17, 2015 @05:46AM
(#10072082)
Interesting concept, but it seems needlessly complicated. What's to prevent websites like, say, the Guardian from declaring themselves as applications?
* Reader browser
* Application browser
The reader browser should show you the "web" in a kindle-like readable experience, just as it does today.
However, the application browser, although it does receive a URL, should not have any HTML page as a default view. Instead, a JavaScript should be first loaded, and from there, following the permissions it requests, it can open new windows, notifications, or any other desktop feature needed, which websites that just need to be read do not need.