|
|
|
|
|
by zer00eyz
806 days ago
|
|
The whole point of a slower moving standard is that you are less likely to fuck yourself. Plan Ahea d At some point whatwg is going to jump the shark. They are going to feature paint themselves into a corner and have to make the choice of "cut off some chunk of the web" or "go forward on a new stack". The all gas no brakes add features like were a start up forget about thoughtful or engineering is a bad way to sustain something. |
|
This of course is actually much more likely (and functionally happened) with pre-WHATWG standards because they'd standardize things that were infeasible and no browser ever implemented, ever.
And at the same time everyone had their own weird nonstandard extensions (does no one remember the whacky stuff like https://developer.mozilla.org/en-US/docs/Glossary/Vendor_Pre... and how absolutely garbage-awful it was for maintainability?)