4 ms·

Okay, but I’m not in the Jai beta, and I have to use the tools available to me…

• zbentley 4y ago
  Nim, D, Go, Rust, and several other languages in this space all offer a similarly integrated toolchain without the drawbacks of legacy build systems. And those are all free and available, unlike Jai.
  • georgyo 4y ago
    This is mostly true, but it is also because there is only one implementation of an these languages. Go for example has a gcc compiler as well. And that compiler has very different options than the one written in go.
    • zbentley 4y ago
      That's not really true, I'm afraid. Go/Rust have alternative compilers as you point out; what does "very different options" have to do with anything? The GGP's statement about "discovering" capabilities is, at least to my interpretation, about the behavior of language features under a given compiler (i.e. autoconf rules for things like "are we using this one buggy version of gcc that can't reliably use vectorized instructions for some common task? If so, drop in an alternative implementation of some common library function"), not the options/flags of the compiler itself. D has multiple supported compilers (https://dlang.org/download.html https://dlang.org/download.html). The simplest one is simpler/more pleasant to use because of the lack of legacy baggage. Nim is a bit of an odd one, in that there's one implementation of the language, but the most common compiler mode emits C code to be compiled on the toolchain of your choice, though the behavioral configuration of the toolchain is handled/defaulted well (at least, well enough I've never had to worry about a multi-stage build system) by the "nim" CLI utility.