[jpace121]

“ Wow is the web a weird application delivery mechanism where people are writing applications and then essentially compiling them down to binaries using WebAssembly, but weirdly shoehorning it into a hypertext framework”

I thought this was an interesting quote from the article that relates back to something I’ve been thinking about as I’ve started to look at writing apps that run any where and realized that forces you into writing a web app, but web apps kind of suck because at the end of the day you’re really writing a website not an app…

I wonder if you could at this point reinvent the browser so it was specialized for web apps not sites, and what that would even look like.

[paxys]

That distinction doesn't matter all that much today. The entire "hypertext framework" part of most single page apps is a generic 10-line index.html. The app bundle can be downloaded and cached indefinitely and work perfectly even offline. This specialized browser for web apps not sites would look like – Chrome.

[tanseydavid]

>> The entire "hypertext framework" part of most single page apps is a generic 10-line index.html.

This statement seems rather misleading. There ultimately ends up being vastly more hypertext delivered to the browser than can be represented by a 10-line html file.

[janalsncm]

I don’t know enough about non-web apps. What sucks about web apps? Speed is definitely a part of it, but I always saw that as a cost of interoperability.