4 ms·
> Imagine a small company trying to write their own web browser from scratch nowadays. It's just not possible! This is also because the web has a firing proble
by Griffinsauce 5y ago
> Imagine a small company trying to write their own web browser from scratch nowadays. It's just not possible!
This is also because the web has a firing problem.
APIs and features barely get deprecated, even when they are obviously superceded. When they do its years and years after the fact. We also just except whacky quirks instead of fixing them and moving on.
A very clear example: we do not need CSS float anymore. It can be removed with zero impact on the development of new websites.
There's a new proposal for date-time features that replace the Date class. Except it won't, they will coexist and you have to support the Date class and all its bullshit indefinitely.
Do we really need anything other than template literals for strings?
I'm not sure what the solution is to these but an ever-growing spec seems like a big part of the problem to me.
- cdirkx 5y agoA new implementation could choose to not add those older features, but there will always be some websites that still rely on them. Who is going to use a website that isn't able to display the sites they want?
- Griffinsauce 5y agoExactly, this problem is not acknowledged or codified so we have no choice but to indefinitely support everything. > Who is going to use a [browser] that isn't able to display the sites they want? Everybody who has more to gain than to lose from it. The perfect solution would of course avoid this problem somehow.
- graftak 5y agoWe don’t need css float for layout hacks anymore, but it’s intended purpose to wrap text around an element is still a valid use case.