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.
I'd say my work has gone in the hands of a few million people and made their lives (mostly) better, along with what all of my coworkers did.
But most importantly, I'm not out there telling people that they suck, they're bad programmers. I'm not the one out there telling people that GC bad, memory ownership bad but also you're stupid if you can't free() memory properly. I'm not the one out there rejecting decades of PL theory, calling academics "believers" and "wrong" [0], I'm not the one throwing shade at every other language, and when criticized on my language, fall back to "uuuuh I make Jai for myself you don't have to use it"
Anyways, if you want a real systems language that's available today and that actually works, Odin exists.
Plenty! Although, it's not limited to iterators: most languages that have first class lambdas/closures behave this way. Kotlin has `it` as the default parameter of any lambda (but only accepts it for single parameter lambdas, two parameters and you need to name them:
>Btw. in for-loops the colon `:` is used inconsistently again, this time for naming the iterator (`foo` in this example:) `for foo: VALUES { ... }`.
Sorry, Jonathan Blow doesn't believe in such silly things as "compiler research" nor "programming language research". Jai gets built by piling up crap on top of crap.
Whereas the brave Go developer is going to rewrite a half baked implementation of Spring Boot for every service that ends up growing a little bit more than expected, all on the default go server. Weeeeeeee
It's not like the kotlin DSL comes without problems. Configuration time is most of the time about doubled compared to Groovy, type hinting and completion often end up being slower _and_ worse than Groovy, and if you're lucky, your IDE suddenly can't find a random extension in your classpath and your entire build.gradle.kts or plugin becomes a red, squiggly mess.
Unfortunately, Gradle is the best build tool I've used for complex systems. And it still fucking sucks.
Let's be honest, most wayland advocates do not give a single shit about people sticking on xorg.
They might care a little bit more when their only interactions are with snarky people going "sO yOu StILl CaN'T tAKe ScReEnShOts oN wAyLaNd haHaHa sHiTtY sOftWare", or legitimate assholes.
Hot take: As a software engineer, or absolutely anything else, don't owe these people anything. I'm building software in the direction that I want to bring it. If they're unhappy, they're free to leave. But to have them come on public forums and call you a jerk, that's just comical.
> I don't understand how that gives you dictatorial power over 100s of users who don't like the changes you've made.
Those hundreds of user are:
1. A vocal minority, most likely. People happy about it don't go on bug trackers to support devs.
2. Not making the software, not part of the decision making process. Don't like the end result ? Fork it if you have the ability. Give constructive criticism if you want and you think the team is receptive to it (or even cares about it. Sometimes, I just don't want your genius idea).
So, yes. They're doing this for free. Don't like it? Fork it, or don't be an ass. If you can't do either of those, the third option is to fuck off.