Earlier quoted context omitted.
The innovative potential of Mojo would be constrained to relatively niche and senior dev circles until they get a Windows release, which probably won't happen anytime soon. Python keeps the throne for now.
I don't understand this premise. And the more I think about it, the less sense it makes. On the grand scale of things, Windows is the niche platform here. For consumer desktop use cases, it is king, but nobody deploys on it for the use cases that the first version of Mojo is optimised for.
Mojo is now open source
31–40 of 108 posts
Re: Mojo is now open source
#32Earlier quoted context omitted.
The innovative potential of Mojo would be constrained to relatively niche and senior dev circles until they get a Windows release, which probably won't happen anytime soon. Python keeps the throne for now.
And Julia as well.
Re: Mojo is now open source
#33Earlier quoted context omitted.
In the category of AI/HPC software Mojo aims to displace (which is my industry), I don't know many people who care that much about running Windows. The software I work on may only run as a Docker image or directly in a Linux/WSL. Mojo is hardly the only tool in the space (currently) lacking Windows support.
I'd put you in the "relatively niche and senior" bucket without even thinking.
Re: Mojo is now open source
#34Earlier quoted context omitted.
And Julia as well.
It's a sad time to be a fan of Julia-- everyone forgets it's there.
For the same reasons I see languages like Python, Java, C# as inferior.
Re: Mojo is now open source
#35Earlier quoted context omitted.
It's a sad time to be a fan of Julia-- everyone forgets it's there.
I was excited to try Julia, but then, as I saw it was an interpreted language, with bulky runtime, slow startup times and bloated library sizes - my initial interest quickly faded. For the same reasons I see languages like Python, Java, C# as inferior.
And inferior to what, the crab?
Re: Mojo is now open source
#36Earlier quoted context omitted.
And Julia as well.
It's a sad time to be a fan of Julia-- everyone forgets it's there.
Re: Mojo is now open source
#37Earlier quoted context omitted.
I was excited to try Julia, but then, as I saw it was an interpreted language, with bulky runtime, slow startup times and bloated library sizes - my initial interest quickly faded. For the same reasons I see languages like Python, Java, C# as inferior.
Java and C# definitely don't belong on the same basket. And inferior to what, the crab?
Re: Mojo is now open source
#38Earlier quoted context omitted.
Java and C# definitely don't belong on the same basket. And inferior to what, the crab?
Inferior to languages that compile to native binaries, not burning dramatically more cpu cycles than necessary.
Re: Mojo is now open source
#39Earlier quoted context omitted.
It's a sad time to be a fan of Julia-- everyone forgets it's there.
I was excited to try Julia, but then, as I saw it was an interpreted language, with bulky runtime, slow startup times and bloated library sizes - my initial interest quickly faded. For the same reasons I see languages like Python, Java, C# as inferior.
Re: Mojo is now open source
#40This is really exciting. I've been using Mojo off and on for side projects over the last two years. (copying from some previous Mojo threads) It's got an ownership system adjacent to Rust, comptime similar to Zig, and a first class dependent type system. Even more exciting, is that uses LLVM (to the best of my understanding) in some novel ways and for more optimizations.
Hm, in docs they say that dependent type system is not first class seems. Is it even dependent? More like refinement types, which seems will be in Rust too.Also HN recently mentioned Rust building similar llvm based integration with GPU. But compared with Python, Julia, Matlab, R, Rust, C, C++ - Mojo feel relief for working with numerics.
Out of those, Julia is the only one that combines Multiple Dispatch and native code, both important for numerics.