3 ms·
> Does that sound familiar? It should, you could use that same description for containers The reminds me of java but with native web browser support instead of
by goalieca 3y ago
> Does that sound familiar? It should, you could use that same description for containers
The reminds me of java but with native web browser support instead of applets.
- coffeebeqn 3y agoThis has all happened before. Java web things, Flash, etc. they all have the same problem that they don’t fit in with semantic web content
- zdragnar 3y agoThat's not why those things died, though. They died because smartphones stopped supporting them, and that combined with advancements in JS engine speed were all it took to get brother vendors to scrap the buggy, security-hole-ridden plugin ecosystem. WASM should hopefully not be bad from a security perspective, but the up-front performance penalty of early demos in downloading megabytes for hello world was painful. More purpose-fit, smaller modules ought to be broadly useful but I'll not be holding my breath. Anything that needs to take over a canvas probably isn't going to be widely adopted outside of some niche things like visual design tools or the occasional game.
- tcfhgj 3y agoMegabytes are certainly an exaggeration, see 285.4 KB for Leptos
- lelanthran 3y ago>> the up-front performance penalty of early demos in downloading megabytes for hello world was painful. > Megabytes are certainly an exaggeration, see 285.4 KB for Leptos Those early demos were certainly quite large. I don't think that I found any early demo of WASM to be under a megabyte, for sometimes quite trivial things.
- paulgb 3y agoFlash and Java Applets both owned a rectangle of the screen. Wasm interacts with the page just like JS does. So in contrast to Flash and Java, Wasm fits in with semantic web content to the same extent that JS does.
- throwaway847599 3y agoJava applets could access the DOM and even run Javascript functions.
- paulgb 3y agoSure, but presumably the ones that “don’t fit in semantic web content” is a reference to the ones that rendered a portion of the page in Java, otherwise the same could be said about JavaScript.
- jeroenhd 3y agoAs you can read in the various comments on here, that's also the model many WASM fans are going for. Google Docs switched to rendering a full screen canvas rather than using the DOM, and Flutter/Compose do the exact same thing. WASM is very much heading in the direction of owning a rectangle on the screen. Plus, Java and Flash embeds could also call Javascript callbacks while leveraging the improved performance of their native plugins.
- paulgb 3y agoGoogle Docs doesn’t use Wasm, from what I can tell. The move towards using canvas/gl/webgpu over DOM for performance is orthogonal to using Wasm. They go together nicely, but if you’re worried about DOM being replaced, Docs is a good example of how that will happen with or without Wasm. Another pattern I’ve seen is to render DOM on top of a canvas, with UI elements done in the DOM, and high-performance graphics on the canvas. This seems to be a good balance. https://x.com/paulgb/status/1688919428740816896?s=46 https://x.com/paulgb/status/1688919428740816896?s=46
- troupo 3y ago
- paulddraper 3y agoThat, but without the proprietary UI
- lmm 3y agoTclets were fully open source and Java applets were mostly open source. It doesn't seem to have helped.
- paulddraper 3y agoPerhaps I should say non-standard/non-native. Java applets used Java Swing UI
- intrasight 3y agoI was sure that "Does that sound familiar" would be followed by the history of Java. There's no VM in Docker.
- pjmlp 3y agoWASM Runtime...
- intrasight 3y agoThat new tech. The article quote was referring to Docker pre-WASM.
- pjmlp 3y agoWhat article? Docker needs a WASM runtime regardless. Some magic incantation has to change those bytecodes into executable code.