Jaremy Creechley

> Why do we need this? It's beyond Atlas's scope and doesn't fit in IMO. It’s not beyond the original scope of Atlas. Narrowing down atlas’s scope has made sense...

Hmmm though I just remembered there is testament. I just recall testament kinda “being meh” for some reason. As in confusing to use. Maybe that was the koch thing. Honestly...

On the note of a nimble replacement, IMO Atlas should also support `build` again as well. Most of that is because adding `atlas install && atlas build` is far easier...

See, I might be too dumb to use Testament: https://gist.github.com/elcritch/2cae045ce132dfd34c703b6653560d71 Ugh I'll have to read the docs instead of running my tests. :P

> The problem here is that Atlas's design says "it won't call Nim for you", it merely sets up a nim.cfg. `atlas test` and `atlas doc` and `atlas build` violate...

What if `test` was a sort of plugin? Essentially Atlas could support plugins for running cmake, or running nim tests, etc. Then technically it's not Atlas invoking Nim, but another...

> What does the preNode step refer to? The `preNode` step ensures a child node has been allocated and setup. If the node exists it just preps the node for...

> The idea of separating user documentation from developer documentation popped into my mind again. This seems more developer oriented. Do you want to make the main README be user...

Ah thanks for testing. I haven't tested the software rendering approach at all. :) Looks like from that link that it'd need to query for certain supported parameters in OpenGL....

I tried making a backend with Boxy and got it working. It looks like it has GLSL version 1.0 shaders, so it may work with the OpenGL 1.0 setup. It's...