2 ms·
1. The idea that these standards need third-party write-ups for basic reference (not tutorial) use boggles my mind. Why is the main standard so unusable that we
by yencabulator 6y ago
1. The idea that these standards need third-party write-ups for basic reference (not tutorial) use boggles my mind. Why is the main standard so unusable that we can't rely on it to explain what a form element is. The web "standards" have a history of this. It's a self-caused problem -- fix the problem, don't paper over it.
2. A lot of this complaint seems to be about needing to repeat manual browser testing regularly. Why is it manual?
3. The web is a bloated, overcomplex, platform with hundreds of talented people full time employed to make it more complex every day. Since it seems HTML+CSS+Javascript cannot be contained inside any line drawn, can we figure out something like a WASM + son-of-DOM simpler reboot that throws out as much of this complexity as possible? As in, stop using the existing HTML tags and default CSS, let the app define new ones along the lines of WebComponents, and make the DOM be just a rendering engine to get things like universal text selection and copy-paste (as opposed to everything just blitting to a canvas and reimplementing that). Of course I'm oversimplifying -- but I really think the world needs an old school "hourglass figure architecture" here to limit this feature creep.