rusterizer VS PortableGL

I've written a simple 3D renderer entirely in Rust from scratch. You can try in an online sandbox here https://dzharvis.github.io/rusterizer/ The renderer was implemented by following these lessons I did not look at the original C++ code, so my code contains hacks or magic numbers in some places :) Anyway, I hope that this can be useful for somebody.

Yeah PortableGL will never be completely fully featured, not even for OpenGL 3.3 since I'll definitely never do the geometry shader and probably not the transform feedback. But specifically it'll never have the earlier immediate mode stuff, or some of the big 4.0 stuff like the tessellation shaders. I have been meaning to add the DSA functions where they make sense. They'd be really simple to implement.

Actually a few days ago someone sent me a pull request adding an interesting project to my README

https://github.com/rswinkle/PortableGL/commit/e0652b4dff266d...

So now if I were to try to sum up all the OpenGL software implementations I can think of,

TinyGL (and modern improved forks) = OpenGL 1.1-1.3 ish

PortableGL: An implementation of OpenGL 3.x-ish in clean C\ (23 comments)

Not entirely related to the subject of OpenGL, but I really like how the author has decided to lay out this project. It's pretty hard to beat the convenience of a single header (or single header/single source) distribution for C libraries, but library development gets progressively harder as the project gets bigger as more code is added to the (usually hard to navigate) header file. Here, the author does their development with multiple files as one normally would, but when a new version is released they run the generate_gl_h[1] script that concatenates everything into a .h file for distribution. Simple yet flexible! This is also how SQLite[2] distributes its builds. It's a pattern that I'm using myself in some unreleased projects.

[1] https://github.com/rswinkle/PortableGL/blob/master/src/gener...