I mean both developing a complete language + compiler toolchain + standard library and developing a game are projects which often take many many years. Rust was started in 2006 and didn't receive a 1.0 release until a decade later in 2015. Go was a bit quicker, starting out in 2007 and releasing a 1.0 in 2012, but I don't think anyone outside of Google really used it until years later.

It really does seem like the people who complain about how long it's taking either have no context for how long this stuff takes. You can knock out a toy language in a month, sure, but growing an actually production ready serious systems language, with a solid compiler which produces optimized code across platforms, and a complete standard library and solid core abstractions, and a good module system, and incremental parallel compilation which scales to millions of LoC, and with innovative language features which aren't in comparable mainstream languages... that takes time.

> Rust was started in 2006 and didn't receive a 1.0 release until a decade later in 2015.

It wasn't widely announced until IIRC 2008, and it was public and in popular use by 2011 or so (long before 1.0 - just as e.g. Zig is definitely pre-1.0, but also very clearly a real language that people are using).

How many years are you planning to wait for Jai? Serious question - if it's still not publicly available in e.g. 2034, are you still going to be saying that's just how long these things take?

Well I'm not waiting for Jai, I'm happily using C++. If Jai eventually comes out and turns out to be a cool language and the tooling becomes available under sane licenses I might pick it up, or I might not. I'm in no rush either way.

If it's still not available in 2034, I guess you can fairly say it's taking a while. But then again, so what; if it comes out in 2036 it comes out in 2036.

>But then again, so what; if it comes out in 2036 it comes out in 2036.

There's this whole 'passing of time', and "we'll all eventually die", thing though, right?

If it comes out in 2036, it's totally irrelevant for a working dev in 2024 to be concerned with it. So that he'll get to use it in a decade? At this point it's already a promise-ware, and it's like it has community adoption to be promising.

Until at least a roadmap is released, Jai is totally irrelevant for a working developer. Even if it's released next month, you can't plan for that.

My opinion is that it's just too big of project for him to handle alone. So it will be in this status forever as other languages catches up. It's just humanly impossible to finish AND be better than other choices AND be done without help

Good news! It doesn't seem to be a project handled by him alone. I don't pay much attention to Blow or his company, but the few times I've watched videos where he does go over progress of the language, he often talks about compiler work other people in the company are doing, and even about hiring people specifically to work only on some part of the compiler.

I hope he can succeed. Language diversity is generally good, but it does look like an uphill battle