Hacker News Reader

Comment by mariusor | Hacker News Reader

Just a warning, this document doesn't reflect very well where Jai is at in 2021.

The best place to get information about the language is this youtube playlist: https://www.youtube.com/playlist?list=PLmV5I2fxaiCKfxMBrNsU1...

However it has a lot of content.

View on HN

I'm not super eager at having to watch a few 1-2 hours videos to even understand why I should use Jai.

jblow seems like a really talented developer. I loved Braid and there's clearly some great work being put into Jai. But if (and this is a big if) he wants to make Jai into a language people use, he should seriously consider putting more effort into the documentation and distribution side.

jai isn't publicly available yet. (It's currently in a private beta.)

It took me a long time to find this out. It never occured to me the source code is private when an author is posting so many videos and discussing about the design of language.

I know. Anyway the playlist is not about why _you_ should use the language but more about why he started developing it and some of the more important steps along the way (2014 - 2021).

The compiler is not out yet, it's in a closed beta to a small number of developers with plans to release later this year (to the best of my knowledge).

From watching some of his Twitch streams, I get the general impression that he really doesn't care if Jai is a language that "people" use. He seems to be developing it basically entirely as a language that he wants to use and whether anyone else outside of his company uses it is almost irrelevant.

Languages are subjects to network effect and in the long term that is what will make or break them. Now, when one has to eventually deal with the wider public (just like when developing any given product addressed at public), it pays to consider its feedback. I understand that he is experienced and that most likely he knows better than what he might get from such feedback. We'll see how this turns out.

>Languages are subjects to network effect and in the long term that is what will make or break them.

That's a circular argument given what's discussed in this thread.

The "make or break them" presupposes the goal is for the language to "break out", whereas the parent said the goal is for the creator to be satisfied and use the language himself.

There tons of languages in domains like gaming where nobody cares if they "break out" or for network effects. People write them to use them themselves.

"the goal is for the creator to be satisfied and use the language himself"

That is only one of the goals. The author is also interested in making that language public at one point, even if that comes as a far secondary concern for him, otherwise he wouldn't have bothered to publish anything.

"That's a circular argument given what's discussed in this thread."

What would you say to "whether anyone else outside of his company uses it is almost irrelevant"?

Well, he's not releasing it generally yet, so it's not fair to criticize not releasing documentation. This was created by someone else. He mentioned that when he open-sources it or soon after, he's planning on releasing the engine from the game Thekla is currently working on, which will provide a good sample of "idiomatic Jai". I'm hoping that good documentation will come with it.

he had a recent interview where he addressed this directly: his philosophy is that there's too much crappy stuff out there that's heavily promoted and branded, and so he's trying to get the language to a place where it's stable and worth using before he does a general release / chooses an actual name. It's in closed beta now.

>...he should seriously consider putting more effort into the documentation and distribution side.

In addition to what other people have said, Blow is explicitly working on documentation over time and closed beta users have access to a fair number of documents detailing both language features and the philosophy behind the language.

One huge reason why the language IS still in closed beta is because Blow believes heavily in not releasing half-assed work. Documentation is a part of that.

The source code is not even published for public access

The page says "Jai could be described as a modern replacement for C"

Rust and Zig are other languages that more or less try to be replacements for C. Without having looked too deeply, it feels like Jai could more or less be described as similar to D (with the -betterC flag, perhaps). Does that seem like a reasonable characterization? Is there something specific that Jai brings to the table that those other languages don't?

The one thing I remember surprising me was that the build scripts were also jai.

I think that is also the case for Zig. The build system is a zig file.

The D compiler has a build script called (imaginatively) build.d (rdmd let's you run a single D file in one step), and although it's not super sophisticated, I'm already convinced that makefiles should be considered harmful if the alternative is something in a real language.

Not only can you actually read the code, you can also express things in a platform agnostic way rather than the inevitable "which make are you actually" bug report

Well D and Rust are more contenders for C++ in terms on how wide their agenda is. D is (unless you opt out ?) GCed, Rust is not but they both pack a lot. Zig on the other truly aims to be a C replacement I believe, trying to avoid it considers its pitfalls (preprocessor, build system, error handling...)

The D GC is written in D so you can opt out as you wish, but the standard library is designed around the GC.

That being said if you are in a situation where you cannot use the GC you probably wouldn't need the stdlib all that much anyway (there's a bunch of alternatives available).

Reply on news.ycombinator.com