so long term planning on wasm raylib; I want compatibility with the good parts of the std, the std is causal about using libc while ldc-wasm half-baked implication is missing a bunch of basically worthless symbols but given the std is 1 million lines of code it will be a perennial problem that I make something work natively, I try it in wasm, it breaks citing a random core lib at a random line; the options I know about are:
- use a "team betterc" personal std that doesn't have the apis I want, apis I know and probably limited
- merge "use libc less" upstream to a std that has been slow to merge changes and probably doesnt care about wasm
- fork the std
- maintain patches to the std that go in and rewrite them live with root :D what could go wrong
- make my own personal std that matches the std api of the parts I use
I hate all these options