31–40 of 77 posts
Sharing a reddit link for the purpose of sharing a youtube video seems weird. WHat's the point of that? Is it to game the HN algorithm somehow?
By any measure except by comparison to a hypothetical counterfactual universe, I think javascript is one of the most successful programming languages of all time, and one that has added more to the world than almost any other. It's like standards: some have better performance characteristics than others, some are more elegant, and so on. But the the best standard is the one everybody actually uses, because that is th…
It is just a scripting language. If it wasn't JavaScript, it would be something else. It hasn't added anything besides lots of crappy code, most of which shouldn't have been written in JavaScript anyway.
I can't understand how anyone could find its moronic semantics bearable.
Earlier quoted context omitted.
not all all. I just have: document.addEventListener("DOMContentLoaded", function() { const go = new Go(); WebAssembly.instantiateStreaming(fetch("/assets/other/json.wasm.gz"), go.importObject).then((result) => { go.run(result.instance); WasmReady('welcome.html'); }); }); and and that's it! Then from go there's nothing I can't do in the DOM.
Does wasm provide synchronous access through the perimeter?
Earlier quoted context omitted.
not all all. I just have: document.addEventListener("DOMContentLoaded", function() { const go = new Go(); WebAssembly.instantiateStreaming(fetch("/assets/other/json.wasm.gz"), go.importObject).then((result) => { go.run(result.instance); WasmReady('welcome.html'); }); }); and and that's it! Then from go there's nothing I can't do in the DOM.
The `new Go();` is doing all the JS that you claim to not be doing.
We've learned a lot and we can re-build new clean stuff based on the new, richer understanding of what actually matters. But as Alan Kay talks about frequently, anything new has to be immediately just as good and usually better than the mediocre, bloated software for people to switch.
"Worse is better" still continues ...
He doesn’t really say much other than it could be better if we used “clean” operating systems and “clean” programming languages, whatever that means.
Instead of the reddit convo, some more discussions here:
Last week: https://news.ycombinator.com/item?id=41064461
Last year:
Actual video (2023): https://www.youtube.com/watch?v=lc5Np9OqDHU Instead of the reddit convo, some more discussions here: Last week: https://news.ycombinator.com/item?id=41064461 Last year: https://news.ycombinator.com/item?id=36241965 https://news.ycombinator.com/item?id=36164909
Earlier quoted context omitted.
His entire point is that it can't be done currently.
so what's the big problem with calling instantiateStreaming? Explain it to me like i'm 5
This hybrid approach that requires JS both at bootstrap and browser-API-interaction time significantly undercuts the benefits of WASM as a javascript replacement for several reasons. Some of those reasons are: this likely means JS will remain supported/enabled/required-for-many-sites in browsers, warts and all, in perpetuity; the advantages of WASM's sandboxability will be mitigated by the presence of a much more permissive runtime that must be present in order to load and run WASM artifacts; more performant/parallel access to browser APIs will remain difficult or impossible; multi-language/multi-build system competence will be needed due to large parts of the ecosystem remaining in browser JS.