3 ms·
There is a serious problem when every new generations of a technology fixates on some problem of its choice and ignores all the others. The issue of binary blob
by romaniv 9y ago
There is a serious problem when every new generations of a technology fixates on some problem of its choice and ignores all the others. The issue of binary blobs didn't go away. What changed is that a lot of developers today don't care about the open nature of the web and are perfectly fine with sacrificing it for faster load times of their JS-saturated websites.
I think a much better approach to this pronblem would be a compression format that's designed specifically for JavaScript. It could still be negotiable, like GZIP, so anyone wanting to see the source would be able to see it. It could also be designed in a way that allows direct parsing without (full?) decompression.
- Yoric 9y agoSo, just to clarify: this is what the JavaScript Binary AST is aiming for. We are not working on the negotiation part for the moment, because that's not part of the JS VM, but this will happen eventually.
- romaniv 9y agoThat's good to hear. Apparently I jumped all the important parts when skimming the article. Appreciate the clarification here.
- lj3 9y ago> What changed is that a lot of developers today don't care about the open nature of the web and are perfectly fine with sacrificing it for faster load times of their JS-saturated websites. I'm one of those developers who couldn't care less about the 'open nature of the web'. I understood the necessity of it to the early, emerging internet, but times have changed. Now that we have secure sandboxes and the web is choking on its own bloat, it's time to shift back to binary blobs.
- deleted 9y ago[deleted]
- tree_of_item 9y agoHow does adding more code to the browser stack prevent the web from "choking on its own bloat"? You need to take things away to reduce bloat, not add them.