Hacker News new | ask | show | jobs
by facu17y 966 days ago
This downvoting to -3 is illustrative of how HN down votes are about territorial warfare, ego, etc. Has nothing to do with logic. You don't like to port your python code to nogil python? I'm gonna downvote you. WTF is wrong with you people.
1 comments

This got a downvote from me because, as a poster of over a decade, I've seen people complain similarly with Java, C#, PHP, C, and every other popular language under the sun where the apparent solution is to move over to a niche language nobody knows and nobody cares about.

It's immature logic from people that lack a sense of perspective of what engineering compromises are and the fact that even substantial language warts don't move the needle as far as justifying language switches.

If you know about Python performance and what's the most you can squeeze from the language, its libraries implemented in C for high performance, and other things in the ecosystem, you already knew if the code you're writing was good for Python or not. If it was, between Cython, C bindings, and NumPy you should be covered. If not, you can drop down to C, Rust and C++ libraries and the slow performance of the glue code is an afterthought.

It is the opinion of an overwhelming majority of coders, who need high-performance code for maybe 5% of what they write (and most of that being code getting run relatively very little), that higher performance is not as high a priority for those users as some people think.

Mojo was mature enough for a person I know in the community who ported their Python port of llama2 to it. Also, others pointed out other languages they would rather use.

The rationalization in your response obfuscate the real reason you were triggered to down vote, which is that you are too emotionally vested in Python and afraid to try a better alternative.

Mojo is just like Crystal and a dozen other predecessors that pretend to imitate the syntax of an existing dynamic language like Python or Ruby and provide some more performance and no other benefit of importance. That has never been enough.
Mojo is still quite far in vaporware land as far as Python compatibility goes, but they do claim to target much higher level of compatibility than eg Crystal.
People want bug-for-bug compatibility when switching costs are high, and that never works out in practice.

An alternative language has to be far superior to its alternatives to justify the switching costs.

In fairness, it worked (quite well) for Typescript.