Just a warning, this document doesn't reflect very well where Jai is at in 2021.<p>The best place to get information about the language is this youtube playlist: <a href="https://www.youtube.com/playlist?list=PLmV5I2fxaiCKfxMBrNsU1kgKJXD3PkyxO" rel="nofollow">https://www.youtube.com/playlist?list=PLmV5I2fxaiCKfxMBrNsU1...</a><p>However it has a lot of content.
> It is still in development and as of yet is unavailable to the general public.<p>Damn. I was hoping that had changed. I'm curious to see the hype, but I'm not into PL stuff enough to dig into a language I can't play with.
If curious see also<p>2018 (a bit) <a href="https://news.ycombinator.com/item?id=16596282" rel="nofollow">https://news.ycombinator.com/item?id=16596282</a><p>2016 <a href="https://news.ycombinator.com/item?id=11086708" rel="nofollow">https://news.ycombinator.com/item?id=11086708</a><p>2015 <a href="https://news.ycombinator.com/item?id=10346985" rel="nofollow">https://news.ycombinator.com/item?id=10346985</a>
I really like that the arrays are a full type that pack their size information. C has always frustrated me on this particular point. One question though : Is the array types passed as a pointer and an int or copied locally ? I guess 1. because 2. would not make much sense (although this the C behaviour for structs in C... I wonder why...)
Jai changed quite a bit since then.<p>For more current info check out beta user's impressions (and the language primer) here: <a href="https://www.youtube.com/watch?v=i1vbvikDiI8" rel="nofollow">https://www.youtube.com/watch?v=i1vbvikDiI8</a> (first video in the series)
Why must every new language use a completely unique syntax?<p>This is so tiring...why can't they just stick to syntax that everyone knows...each one has to reinvent random new syntax and destroy old conventions that people already know thus needlesly creating friction.