Jai-Community-Library VS EmeraldC

Comparatively

> Incremental rebuilds cause a lot of compilation problems, bugs, and errors. Incremental rebuilds are also slow due to the amount of in between files generated between builds. Jai will contain no incremental rebuild steps. All will be compiled in one fresh compilation. This means that the compiler will need to run fast with high performance. The eventual goal is to compile a 1 million lines of code in 1 second, but as of right now, the compiler can only do 250,000 lines in 1 second.

https://github.com/Jai-Community/Jai-Community-Library/wiki/...

Either ask very politely for years, or be in denial like half the Jai community that writes Jai but is never able to compile it.

Yes, there is a whole Jai community wiki made from half cobbled together knowledge (https://github.com/Jai-Community/Jai-Community-Library/wiki), and a super secret discord made for the super elite, non-compiler-having plebs are banned.

- Philosophical approaches behind project or lack thereof.

Now on the personal, subjective note, the more I look, the more I want to avoid V and get my hands on Jai [1][2]

[1] https://github.com/Jai-Community/Jai-Community-Library/wiki/...

Here's a community wiki that's been kept up-to-date https://github.com/Jai-Community/Jai-Community-Library/wiki

Also this one: https://github.com/Jai-Community/Jai-Community-Library/wiki

There is also the Jai community library, which contains pretty much all the information about the language currently. https://github.com/Jai-Community/Jai-Community-Library