4 ms·
The parent’s point is that, if all these things were browser JS runtime features, there’d be no tradeoff to be made. They’d be “free.” If every JS page in the
by derefr 7y ago
The parent’s point is that, if all these things were browser JS runtime features, there’d be no tradeoff to be made. They’d be “free.”
If every JS page in the world today includes the same line of code, isn’t it obviously the fault of browser makers for not making that line of code part of the JS prelude and thereby making it “free”?
- worble 7y agoThat's fine, and if they do end up being part of the JS runtime, then great! But right now they don't, so by including those you are actively having to pay the cost of doing so. My point of contention with the parent post is that these features are requirements for a webpage "to be barely useable". You can absolutely make great websites and webpages without these.
- moltar 7y agoThat’s a slippery slope. We’ll eventually turn the browser into an OS. And more features = more surface area for bugs.
- kalleboo 7y agoIt's increasingly looking like our two options are either 1. Turning the browser into an OS (what Google is working toward) 2. Downloading an OS on each page load (What webassembly is working toward)
- mekoka 7y agoAn OS? An exaggeration maybe, but only slight. The browser is pretty much its own environment already. It's been the case for decades. It can display text, process a variety of media, and run programs (written in JavaScript). The main cause of frustration at this point is that, compared to other popular programmable environments (C, PHP, Python, node.js, etc), where some real focus is put into evolving the language along with a variety of primary development tools, people in charge of the browser's ecosystem seem to still be coming to terms with the programmable part of its identity. All the dilly-dallying results in community efforts that pile on top of each other to create all this bloat that is carried from one tool to the next framework.