depoverflow VS ancient-3d-for-turboc

I go one further. If I do use a piece of code from Stack overflow (usually a workaround for some API pain point or specific technical gimmick), I linked to the answer from a comment. I then built a tool to notify me if that answer gets new comments or new answers are added. [1] Similar to how I check for new versions of my npm/pip/gem/cargo dependencies, I check for new info on my Stack overflow dependencies.

[1]: https://github.com/remram44/depoverflow

Nice! This prompted me to post my own code from the same era: https://github.com/pjc50/ancient-3d-for-turboc

I guess I should add screenshots.

Twenty-five years ago, slightly before I was an undergraduate, I got hold of the PC Games Programmers Encyclopedia http://bespin.org/~qz/pc-gpe/ and built myself a software renderer. You can see it on github: https://github.com/pjc50/ancient-3d-for-turboc

Software matrix multiplication is a perfectly reasonable way of doing 3D graphics, when you don't have a GPU. They were just starting to become a consumer product at that time: https://fabiensanglard.net/3dfx_sst1/

The set of things you had to worry about is just .. different. My ancient programmer credentials from 1996: https://github.com/pjc50/ancient-3d-for-turboc

Back in the day, you had:

- single processor

Is this where I post the code I wrote twenty-five years ago to do 16-bit fixed-point 3D rendering? https://github.com/pjc50/ancient-3d-for-turboc

The target architecture was a 33MHz 486 PC running in "real" (ie sixteen-bit) mode. While hardware floating point was sometimes available (DX systems) it was quite slow.