2 ms·

Creating a new language in the age of AI seems kind of pointless. I don't write code by hand anymore, I only review it and I prefer it to be in a language which

by mono442 2mo ago

Creating a new language in the age of AI seems kind of pointless. I don't write code by hand anymore, I only review it and I prefer it to be in a language which I already know since investing time in learning another language doesn't make sense at this point.

tfrancisl 2mo ago
this language predates the rise of "AI" (you probably mean harnessed LLMs, but I'll forgive you) by several years. This is the 1.0 release.
- winding 2mo ago
  This is the team behind MLIR, they have been in this field for 10 years or so.
- ainch 2mo ago
  Does it? Mojo was announced 6 months after ChatGPT was released.
catoc 2mo ago
Pointless? If compiled mojo is faster, more memory-safe, and more hardware independent, that doesn’t seem pointless at all to me. (And now in the age of LLMs, the barriers to get started with a new programming language are lower than ever)
- pjmlp 2mo ago
  Eventually we will all be writing COBOL and how English turns into machine code is irrelevant.
nylonstrung 2mo ago
Do you know CUDA or Triton? The point of Mojo was to replace GPU kernel programming langs with a Pythonic one that was more familiar
- well_ackshually 2mo ago
  And Mojo will die because nvidia is not interested in maintaining any semblance of backwards compatibility when it comes to CUDA. It's going to be a perpetual race forwards, and whenever nvidia upgrades CUDA, you're going to be stuck there twiddling your thumbs and waiting for Mojo to become compatible. Additionally, anyone who has seen how Swift evolved should be wary of Lattner saying "the language is mostly stable", or even "the language is released".
  - Conscat 2mo ago
    It's not true that Nvidia doesn't care about CUDA backwards compatibility. The invention of TileIR was motivated entirely by that problem. GPU architectures are supported by the full tool suites for at least 10 years by CUDA (that's longer than they are for graphics). Nvidia is also a major contributor to MLIR, which they use for TileIR and ClangIR, so should a compatibility break occur it wouldn't be entirely up to Mojo to fix it.
    - mathisfun123 2mo ago
      None of these things are true except the ClangIR thing
jhatemyjob 2mo ago
Sounds like you're just lazy. Which is fine. You'll probably have a okay career. But not a great one.

by mono442 2mo ago

tfrancisl 2mo ago

this language predates the rise of "AI" (you probably mean harnessed LLMs, but I'll forgive you) by several years. This is the 1.0 release.

winding 2mo ago
This is the team behind MLIR, they have been in this field for 10 years or so.
ainch 2mo ago
Does it? Mojo was announced 6 months after ChatGPT was released.

catoc 2mo ago

Pointless? If compiled mojo is faster, more memory-safe, and more hardware independent, that doesn’t seem pointless at all to me. (And now in the age of LLMs, the barriers to get started with a new programming language are lower than ever)

pjmlp 2mo ago
Eventually we will all be writing COBOL and how English turns into machine code is irrelevant.

nylonstrung 2mo ago

Do you know CUDA or Triton? The point of Mojo was to replace GPU kernel programming langs with a Pythonic one that was more familiar

well_ackshually 2mo ago
And Mojo will die because nvidia is not interested in maintaining any semblance of backwards compatibility when it comes to CUDA. It's going to be a perpetual race forwards, and whenever nvidia upgrades CUDA, you're going to be stuck there twiddling your thumbs and waiting for Mojo to become compatible. Additionally, anyone who has seen how Swift evolved should be wary of Lattner saying "the language is mostly stable", or even "the language is released".
- Conscat 2mo ago
  It's not true that Nvidia doesn't care about CUDA backwards compatibility. The invention of TileIR was motivated entirely by that problem. GPU architectures are supported by the full tool suites for at least 10 years by CUDA (that's longer than they are for graphics). Nvidia is also a major contributor to MLIR, which they use for TileIR and ClangIR, so should a compatibility break occur it wouldn't be entirely up to Mojo to fix it.
  - mathisfun123 2mo ago
    None of these things are true except the ClangIR thing

jhatemyjob 2mo ago

Sounds like you're just lazy. Which is fine. You'll probably have a okay career. But not a great one.