But I wasn't even sure what problem does it solves. Looks like its completely missing from the regular discussion / news outlets. Every 1-2 years some barely visible post/article reminds me it even exists...
At this point "developers" these days sound a lot more like consumers than those who actually do research on a tool that solves a problem. Ocaml is barely mentioned in the news and rarely HNers here use that language, but it is Jane Street that maintains and uses it.
Judging by hype isn't a great way of evaluating a language. I am not going to check the entire Nvidia stack, from CUDA, to CUTLASS to cuDNN and even on PyTorch's side just to solve a runtime error that could have originated from either place when Mojo solves all of that.
Jane Street's use of OCamel gives them a comparative advantage in hiring. Many devs put a premium on the tools they use. Same story with Anduril/Mercury using Haskell. You can run a successful prop trading firm/weapons design shop/startup-banking(?) platform without these things. They differentiate you from your competitors by being cool, not by being the best technical solution. If anything they were otherwise unprove at scale and out of pure engineering consideration a gamble. Developers are consumers.
At this point "developers" these days sound a lot more like consumers than those who actually do research on a tool that solves a problem.
No need for snarky comments. These days tools/frameworks/languages/libraries/etc are popping all the time. Do you expect people to research every simple signal they catch in the wild?
The interesting opportunity in 2026 for languages is that an LLM doesn't complain if there's an ecosystem or whether any other LLMs or people are using a language, they'll just write the code in whatever language you tell it to. Already authors are writing languages with features aimed at making it more more attractive for AI to write than people. Also great for working with research languages. I just used AI to write a Halide program and I wouldn't have bothered to do so before, for the reasons you state.
Comments
At this point "developers" these days sound a lot more like consumers than those who actually do research on a tool that solves a problem. Ocaml is barely mentioned in the news and rarely HNers here use that language, but it is Jane Street that maintains and uses it.
Judging by hype isn't a great way of evaluating a language. I am not going to check the entire Nvidia stack, from CUDA, to CUTLASS to cuDNN and even on PyTorch's side just to solve a runtime error that could have originated from either place when Mojo solves all of that.
Jane Street's use of OCamel gives them a comparative advantage in hiring. Many devs put a premium on the tools they use. Same story with Anduril/Mercury using Haskell. You can run a successful prop trading firm/weapons design shop/startup-banking(?) platform without these things. They differentiate you from your competitors by being cool, not by being the best technical solution. If anything they were otherwise unprove at scale and out of pure engineering consideration a gamble. Developers are consumers.
No need for snarky comments. These days tools/frameworks/languages/libraries/etc are popping all the time. Do you expect people to research every simple signal they catch in the wild?
How noob do you have to be to really feel this way lol
Edit: a language is by definition an ecosystem. Learning/using a language that no one else uses is completely pointless.
The interesting opportunity in 2026 for languages is that an LLM doesn't complain if there's an ecosystem or whether any other LLMs or people are using a language, they'll just write the code in whatever language you tell it to. Already authors are writing languages with features aimed at making it more more attractive for AI to write than people. Also great for working with research languages. I just used AI to write a Halide program and I wouldn't have bothered to do so before, for the reasons you state.