Hacker News new | ask | show | jobs
by systemvoltage 1322 days ago
I mean, I can understand the challenge of making sure everything works well across browsers so that should mean that we use standard things and avoid non-standard APIs. Otherwise, we're just feeding the shiny Chrome monster more fodder to engulf this fucking planet.

May be we should just got back to native apps? Hell, native apps that do not connect to the internet. That'd be glorious actually. Problem with browser based apps is that you have zero control over versioning. Server serves, you get the fix. No option to request a particular version of the app. Don't like the new version? Tough luck. Server issues? Go outside.

You know there is something to be said about code/binaries residing on your computer. Call me old fashioned.

1 comments

Making sure everything works on all platforms is often just as hard or harder than making sure it works on all browsers and due to basically non-existent security on desktop operating systems, downloading apps comes with a lot of risk.

What we need is a new app runtime with a unified permission-based API across platforms. All the OS-agnostic parts of that runtime would be a huge pain to develop, so all platforms would probably settle on a shared open source implementation and only implement OS-specific "adapters" for the native stuff.

What I've done there, is reinvented Electron...fuck....

Electron is Chrome.
Yes, I know, hence the "...fuck..."