4 ms·
> the level of crazy complexity and backward compatibility in html/css/js/wasm processing Most people don't need insane levels of backwards compatibility or in
by JumpCrisscross 2y ago
> the level of crazy complexity and backward compatibility in html/css/js/wasm processing
Most people don't need insane levels of backwards compatibility or intense PWA support. That's just cruft that slows everything down and increases the attack surface for, to the user, no real gain.
Perhaps what we need is a lot of lightweight general-use browsers (based on a small number of engines) and then some heavyweight power-user browsers that can WASM to their hearts' content.
- sebmellen 2y agoWe use WASM in web apps that are used by a very large number of “regular” consumers. It would be stupid to kill that off.
- JumpCrisscross 2y ago> We use WASM in web apps that are used by a very large number of “regular” consumers. It would be stupid to kill that off. Large numbers of users use lots of features. That doesn't change that most of them use none of them. WASM would continue to exist. It just doesn't need to be in every browser.
- sitkack 2y agoWho said we have to kill off Wasm, Wasm (minus SIMD) is extremely simple and allows the user (the webdev) to ship the complexity, and not build the complexity into the browser itself.
- akdor1154 2y ago> Most people don't need No, what you mean is 'most greenfield web dev projects don't need...'. Most people do need those things, because assuming there's no civilisation spanning project to literally rewrite 90% of the web, without them their sites would break.
- JumpCrisscross 2y ago> Most people do need those things, because assuming there's no civilisation spanning project to literally rewrite 90% of the web, without them their sites would break Sites most people visit do not require backwards compatiblity. And aside from like Google Docs, I doubt most folk are doing anything with WASM (outside plugins). Look, in a world where Google subsidises browser development, this isn't an issue. We don't need to compromise. But if that funding stream disappears, you do have to compromise. And I'd argue a simple browser doing away with some of the more-complicated stuff would be (a) maintainable and (b) popular enough to pay itself back.
- rcxdude 2y agoMaintainable, maybe. Popular, no. A browser where a good chunk of the web doesn't work is a browser that almost no-one will use.
- JumpCrisscross 2y ago> browser where a good chunk of the web doesn't work is a browser that almost no-one will use I think it could—it’s sort of the case on mobile—but it’s not a view I hold with the strongest conviction.
- immibis 2y agoUnless you can make it so the only part that doesn't work is the bad part. A browser where ads don't work and tracking doesn't work but everything else works is a good browser.
- Ekaros 2y agoRewriting everything seem to have been regular exercise in general... So I don't see problems with doing it once more. How many sites are actually say older than 5 years. And how much work would they need?
- deeThrow94 2y agoWell ok, we can stuff browsers in vms for archival purposes. That doesn't mean we need to support existing sites with future browsers.