2 ms·
Complexity builds in a thing until it becomes too heavy to operate in its original environment, a lighter thing more adapted to the current ecosystem replaces i
by sitkack 8y ago
Complexity builds in a thing until it becomes too heavy to operate in its original environment, a lighter thing more adapted to the current ecosystem replaces it.
You see this in Wikipedia pages on Mathematics, they start small and succinct. Then the Mathematicians move in and make it correct and thorough. And then they keep doing this, until only Mathematicians can understand and edit it.
This exactly mirrors browser evolution. It would be nearly impossible to create a new engine, because the existing ones have accreted over time and staffed > 10M/Y in salaries. Developers are like complexity sponges. Budgets, timelines, cpu cycles, memory, latency. Any resource will be consumed by even a small number of developers on the corporate dole.
The web spec maintainers should have a total complexity budget for the thing they are specifying.
The next browser that comes out, will run in a browser using WASM and render using Canvas. It will have to, there is no other way.
- andrewmcwatters 8y agoAll of that's bullshit when you realize WHATWG and W3C are controlled by browser marketshare majorities. Create a browser that people want that sheds 99% of the bullshit APIs and now you have momentum. It doesn't matter whether or not your browser supports WebGPU or WASM when no one cares to use it because they enjoy a browser with built-in ad blocking or resource limits that prevent idiot developers from offload 10s of megabytes onto them. Protect users and make them your number one priority and everything else is bullshit. Firefox forgot this and lost to Chrome. Microsoft woke up too late and played catchup, and they're still playing it, too.