4 ms·
Every time I hear the word Webassembly I always imagine that one day the browser itself will be written in/compiled to webassembly and eventually the entire op
by ToFab123 8y ago
Every time I hear the word Webassembly I always imagine that one day the browser itself will be written in/compiled to webassembly and eventually the entire operating system will be too. Isn't that the natural end game for webassembly?
- danmaz74 8y agoRegarding the OS, experience tells me this won't happen - very specialised tools are almost always better at very specialised tasks.
- colek42 8y agoyour wait is over. https://bellard.org/jslinux/vm.html?url=https://bellard.org/jslinux/win2k.cfg&mem=192&graphic=1&w=1024&h=768 https://bellard.org/jslinux/vm.html?url=https://bellard.org/...
- fiedzia 8y agoIts a bad idea. You will ignore all the benefits of running native code: performance and access to low level features.You will not gain portability because every platform will have different APIs - those are not part of wasm project.
- pjmlp 8y agoThat bad idea is how mainframes user space applications work, and is partially adopted across watchOS, Android, ChromeOS, webOS, Windows/UWP and Garmin apps.
- fiedzia 8y agoIts certainly not how the OS and its runtime works. It may make sense when you have to support range of different hardware architectures, but its not really something you want to have by design. Limited range of supported hardware and native code will always be better.
- majewsky 8y agoI think colek42's comment was more tongue-in-cheek.
- jmcqk6 8y agoRelevant: https://www.destroyallsoftware.com/talks/the-birth-and-death-of-javascript https://www.destroyallsoftware.com/talks/the-birth-and-death...
- ToFab123 8y agoSo everything is eventually going to WebAssembly. Eventually.
- fnord123 8y agoHuge swathes of Firefox are already written in Javascript.