News for hackers. Stuff that matters.
Re:Mojo: The usability of Python with the performance of C by anakaine on Friday September 22, 2023 @07:18PM (#37619032)
They've also claimed both on the page and in the podcast that certain testing reveals a 68,000x speed up vs Python. That's probably true in a select case, but this is why you use libraries in Python - to make use of all the hard work that already exists in C/C++ in those libraries, with Python serving as a high level and far easier to write functional wrapper. Ie anyone serious about performance isn't going to be looking at that metric seriously, rather they're going to be asking what the real performance gains are vs standard practice. In that case the answer seems to be rather roughly a 1.5x speed up based on what's on the performance page of their site when comparing to PyTorch and CUDA, which is a more realistic scenario.

I am curious about how much work the compiler does to automatically identify available hardware and distribute the load on its own vs how much you need to specify as a developer.

Re:Mojo: The usability of Python with the performance of C by nottorp on Saturday September 23, 2023 @04:13AM (#37621520)
All I know from the news is they have a marketing team that decided to jump on the AI hype bandwagon. Plus the aforementioned outlandish performance claims.

Unfortunately marketing like this tends to trigger an equal and opposite reaction in me.

Anyone with AI programming experience can comment on whether they have made any specific believable claims about performance?

Re:Mojo: The usability of Python with the performance of C by singularity2001 on Saturday September 23, 2023 @04:42AM (#37621627)
If it wasn't for Chris Lattner I'd put Mojo in the same bucket as V thanks to said dissociated marketing team
Re:Mojo: The usability of Python with the performance of C by nottorp on Saturday September 23, 2023 @05:15AM (#37621736)
Hey, V and R are nice language names. How do you search for them with the current engines?

And that company… whatsitsname… X?

Re:Mojo: The usability of Python with the performance of C by Hikikomori on Saturday September 23, 2023 @07:19AM (#37622213)
How do you search for C?
Re:Mojo: The usability of Python with the performance of C by nottorp on Saturday September 23, 2023 @07:52AM (#37622435)
You type Rust and someone has rewritten the C application in it already.

In C’s defense it was made before search engines.

Re:Mojo: The usability of Python with the performance of C by goku12 on Saturday September 23, 2023 @08:11AM (#37622578)
It's quite easy for languages. You just append 'lang' or language to the name. Works even for single letter languages like C, D, R and V.
Re:Mojo: The usability of Python with the performance of C by hashtag-til on Saturday September 23, 2023 @04:43AM (#37621630)
Still early days to see whether this is niche or mainstream.

As of today, I’d bet it is niche like Julia, R, etc.

Re:Mojo: The usability of Python with the performance of C by coldtea on Saturday September 23, 2023 @04:17AM (#37621536)
>That's probably true in a select case, but this is why you use libraries in Python - to make use of all the hard work that already exists in C/C++ in those libraries, with Python serving as a high level and far easier to write functional wrapper.

Yes, but that's also the issue they address. That you cant just write plain Python for something not covered by libraries and have it be fast. You need to then mess with extending with C, Cython, and so on.

Re:Mojo: The usability of Python with the performance of C by kbrkbr on Saturday September 23, 2023 @07:14AM (#37622182)
Or you use numba [1]. Then you can use a subset of plain Python.

[1] https://numba.pydata.org/

Re:Mojo: The usability of Python with the performance of C by taway1237 on Saturday September 23, 2023 @07:49AM (#37622403)
Why is cython (python-like fast language) worse than mojo (python-like fast language)?
Re:Mojo: The usability of Python with the performance of C by CoreyFieldens on Saturday September 23, 2023 @11:37AM (#37624227)
There's no a strong reason to use Mojo over cython right now, but if Mojo can deliver on their claims, I think there will be. Mojo will have a borrow checker, better IDE support, support overloading, and better SIMD support are things that stick out to me.
Re:Mojo: The usability of Python with the performance of C by coldtea on Saturday September 23, 2023 @01:14PM (#37625226)
Aside from the rest of stuff they offer (and higher speed, if they're telling the truth) Mojo is also a standalone language you can use, whereas Cython is meant for dual-mode use alongside Python.