3 ms·
It’s also “conventional wisdom” that (especially?) with the web, there’s The Way It Should Work, and then there’s The Way It Actually Works, which is all the qu
by bch 3y ago
It’s also “conventional wisdom” that (especially?) with the web, there’s The Way It Should Work, and then there’s The Way It Actually Works, which is all the quirks, etc.
I’ve not completed an entire server or browser, so not speaking from implementation experience, just the word on the street.
Is that stale information now?
- olliej 3y agoThe whole whatwg ES3.1/5 saga was dealing with the specs saying what they wanted the world to be (which they did badly and incompletely, and frequently in direct contradiction with) and what browsers needed to do (the “quirks”). The spec as produced by whatwg and the browser vendors actually matched reality, didn’t have ambiguity (or rather any ambiguity that was missed is considered a spec bug/error) and could actually be used to make a browser.
- bch 3y agoThat’s heartening to hear. I appreciate you taking the time to point this out.
- Cyberdog 3y agoMostly stale, yes, thanks in some part to the solidification of the specs that the interview touches on. “Quirks mode” is still a thing to some degree in browser engines, but you’ll get farther than ever adhering to the spec.
- bch 3y agoGood to know. Listened to the full interview, and definitely rooting for Andreas et al with Ladybird.