3 ms·
I feel any article on a new language should have at least a partial spec and preferably at least a rudimentary interpreter or compiler. Otherwise what’s the poi
by olliej 8y ago
I feel any article on a new language should have at least a partial spec and preferably at least a rudimentary interpreter or compiler. Otherwise what’s the point of the article? Especially when it’s lobbing around things like 50% win for instance.
The only actual information I can find about it is videos, which is kind of useless.
- erikpukinskis 8y agoI am a little disappointed he hasn’t released the source, but I am also sympathetic. He wants to be free to change major things about the language while he’s designing it, and that’s harder if other people are using it. That said, if you want to know what Jai is about, I recommend starting from his first video: https://youtu.be/TH9VCN6UkyQ https://youtu.be/TH9VCN6UkyQ The first couple dozen videos are all pretty dense, with him presenting the basics of the language pretty efficiently. (His more recent vids are more like development vlogs) Yes, videos are slow, but for me I don’t think I would’ve appreciated his design choices without all the context. I also found watching his process for inventing the language extremely instructive, just as a programmer. It has substantially formed my own process and thinking over the last few years.
- olliej 8y agoI don’t even care about the source, and like I said video presentations about a language aren’t meaningful to me - it’s super easy to not actually touch on any of the things that are actually hard problems in your presentation if you don’t actually provide the full information. A lot of language decisions are the result of how you handle the edgecases, and how they interact with the rest of the semantics of the language. When thought isn’t given to that you get wonderful things like == in JavaScript (the absurd appearing behaviour is completely consistent with the internal semantics of the language - the weirdness is the result of other language features happening during evaluation)
- geezerjay 8y ago> He wants to be free to change major things about the language while he’s designing it, and that’s harder if other people are using it. I don't se why, if proper versioning is implemented.
- Doxin 8y agoYou'd have to implement proper versioning for one, which takes nonzero effort. Furthermore people being people, they'll complain about breaking changes regardless.
- deleted 8y ago[deleted]
- jcalabro 8y agoMy understanding is that the new language hasn't been released yet and the specs and source will be released within the next year or two.
- olliej 8y agoYes, that’s my point: why are we getting an article that makes developer performance claims about a new language, without even the most basic information about that language?