3 ms·
Well, it's good to see that the browser developers have finally conceded total defeat on Javascript as the basis for their platform, and are now simply construc
by fuckjavascript 13y ago
Well, it's good to see that the browser developers have finally conceded total defeat on Javascript as the basis for their platform, and are now simply constructing a nice little low-level virtual machine for general compilation. Granted, they're still hypocritically trying to keep up appearances by sharing as much machinery as possible with their Javascript VM, but nobody's perfect, I guess.
- fuckjavascript 13y agoSnarky tone aside, care to explain what is inaccurate or unhelpful in this comment? There is a lesson to be learned from the debacle of browser design about ignoring what worked in the past. Does anyone seriously dispute, now that they have FINALLY constructed a VM for low-level code execution combined with some primitive APIs, that the browser as a document viewer with Javascript and DOM banged on is a completely and utterly BUNGLED design? Once you have a GOOD programming environment you can simply create your document viewer as an application inside it! And now that it's 2013 I expect more than old ideas done badly. For example, at this point I would go further and say that the sandboxing in the browser should be handled by the VMM, not by the optimizer! The language should provide portability, not safety. That way optimizations can be as aggressive as you like without worrying about security. But hey let's throw a whole document browser and JIT into the trusted base of this distributed computing platform. I got nothing but ridicule and talk about how the "web" was special from people here on HN in the past when I tried to make these suggestions. Turns out this was utter garbage and the web is like any other programming platform - except designed and used by absolute chimps.