15 ms·
> Where is the specification explicitly asking for it? Edit: actually check the docs [1], there are some specs. But anyway, assuming that memo was all... I ne
by toast0 3y ago
> Where is the specification explicitly asking for it?
Edit: actually check the docs [1], there are some specs. But anyway, assuming that memo was all...
I never worked for Microsoft, and I know they did do some real design and specification work in this time period, but in my experience, this looks like as much of a specification as I usually get:
> Microsoft Senior Vice President Brad Silverberg later sent another memo, stating: "What the [user] is supposed to do is feel uncomfortable, and when he has bugs, suspect that the problem is DR-DOS and then go out to buy MS-DOS."
Tell me what the user's outcome is (user with DR-DOS is uncomfortable and thinks they have bugs), tell me what the desired user response is (buy MS-DOS and retry), and let me figure out the rest.
Sounds like detect DR-DOS explicitly or implicitly, and fail occassionally, and cast asperssions in the error messages. Something like relying on internal layout of memory where MS-DOS always does it one way but DR-DOS doesn't always would be great (add comments to make sure MS engineers don't change it!) ; but I think they went with direct detection and intentional breakage.
I don't think this was a good choice for MS, but I don't think the specification was unclear even if it wasn't detailed. I've done similar work that I don't feel bad about; unapproved 3rd party clients were using my service and I held them to a very strict API; not my fault they didn't have API docs and only reverse engineered 2/3rds of the requests.
[1] https://web.archive.org/web/20180803194008/http://antitrust.slated.org/www.iowaconsumercase.org/011607/1000/PX01133.pdf https://web.archive.org/web/20180803194008/http://antitrust....