News for hackers. Stuff that matters.
Re:We're building a browser when it's supposed to be impossible by cxr on Tuesday April 11, 2023 @02:16PM (#35528983)
> A more detailed spec [...] means more actual code for someone to write.

No, it doesn't. A detailed spec has the same amount of code to write as one with less detail; for the types of specs relevant to this discussion, the requirements (does what the other browser do) exist whether they're made explicit in the spec or not. More code is a consequence of an increase in requirements, not detail.

In any case, neither are exercises that are I/O bound to begin with.

Re:We're building a browser when it's supposed to be impossible by giantrobot on Tuesday April 11, 2023 @04:14PM (#35530874)
No. If a spec doesn't define a behavior code can jump to some "undefined" handler which could be anything from a no-op to some quirks mode. Unless you're Microsoft writing specs "do what Word 97 does", copying the behavior of existing browsers is not a specification.
Re:We're building a browser when it's supposed to be impossible by cxr on Tuesday April 11, 2023 @05:06PM (#35531567)
Please don't ignore the context. (An appropriate response would have been, "Oh shit, I hadn't considered that," rather than treating this as something to "win" and continuing to commit yourself to an untenable position.) We are talking about Web browsers.

You don't, in reality, have the latitude to do "anything from a no-op to some quirks mode" of your choice. The requirement is absolutely the one stated: to be compatible with what other browsers are doing. If your browser doesn't satisfy that requirement, then you break the Web, whether the spec is a hundred million words or a hundred. No amount of pointing at a standard and arguing that it doesn't specify clearly defined behavior in some area will ever be enough to teach a site to be able to say, "Oh, I'll just unbreak myself then so you can go ahead and view/use this page on your computer."

Besides that, even if you were right—and to be clear, you aren't—that doesn't change the fact that, again, arguing for underspecification because "a couple defined values" isn't as much "actual code" that "still needs to be written" is an argument that approaches the problem as if it's I/O bound, but it's not.