3 ms·
It seems most people here are concerned about the readability of web content. Text is already gone with SPAs and React. The only reason we still have an index-a
by csomar 2y ago
It seems most people here are concerned about the readability of web content. Text is already gone with SPAs and React. The only reason we still have an index-able web is because of Google and websites still want to get indexed and ranked. In fact, I'd say Wasm is probably better for text since now you have to provide text in a raw format (ie: JSON) for it to be linked/indexed which is much better than trying to crawl incomprehensible HTML.
I'd say the biggest bottleneck for WASM adoption is the current "establishment" of computing. In order to serve a simple web application, you need an Operating System, Networking stack, a Web Server, a language interpreter, etc... With WASM, all of this disappears and get abstracted away behind a single (or few) solutions. Instead of paying for a full virtual machine to process a few web requests that sits idly for 90% of the time, you only pay for CPU time when your worker is computing stuff (Durable Objects).
There is little incentive for the industry as a whole to move to this model since the end user is the one who is paying for all of this compute. Maybe the Chinese will figure this out and finally push toward that direction.
- deleted 2y ago[deleted]
- guelo 2y agoWhat do you mean that Text is already gone? SPAs and React render plain HTML.
- pjmlp 2y agoThey do, but anyone trying to see how a Website works will find the developer tools as usable as with any browser plugin, unless they have the right plugins installed, and running the developer build.
- csomar 2y agoInside the browser but the code is gibberish/chunked and the HTML is not there until the component is mounted.