Das C. ( D as C )
I remember Vectorflow for sparse neural networks.
We have a wonderful conference every year in London. The last one was particularly nice - lots of people, everyone had a good time (especially myself).
https://youtu.be/V2YwTIIMEeU?si=To2DBlzz30XAUptN
https://dlang.org/blog/2022/02/19/how-i-taught-the-d-program...
(Once you have an internal D ecosystem, you start selecting for D developers, who then prefer to keep using D, and so it persists.)
Not one of the tech giants, but not a small company either: https://www.weka.io/
In this world, D was, while not a common choice, also not an unexpected one. The most common language for these sorts of products is C... but it's not the kind of C you'd find in books about the language. It's C that's heavily modded to remove or replace a bunch of stuff. D just happened to align well with what people running the project would've done to C anyways.
Also, in this context the existence of libraries doesn't matter, as almost everything is going to be written from scratch anyways. Nor does learning the language matter, since the internal infrastructure and learning how C was modified to fit the project goals would take the same time as learning another language.
To be honest, I really liked to work in that environment. Not because of any of D's features. I just hate being in the constant fear that I will not be allowed to do something that makes perfect sense, and instead coerced into idiotic workarounds that pretend to solve the problem. Which is what happens when you are required to use third-party libraries and they absolutely don't anticipate your use-case. It's the place where I was closest to being proud of what I was doing. Unlike most day jobs I had, where I felt like I need some extra time in the shower just to not feel dirty by writing code I knew full well should've never been written.
> Our backend is mostly implemented in OCaml with some D and C++.