Slashdot Mirror
How Rust Can Replace C In Python Libraries (infoworld.com)
An anonymous reader quotes InfoWorld:
Proponents of Rust, the language engineered by Mozilla to give developers both speed and memory safety, are stumping for the language as a long-term replacement for C and C++. But replacing software written in these languages can be a difficult, long-term project. One place where Rust could supplant C in the short term is in the traditionally C libraries used in other languages... [A] new spate of projects are making it easier to develop Rust libraries with convenient bindings to Python -- and to deploy Python packages that have Rust binaries.
The article specifically highlights these four new projects:
The article specifically highlights these four new projects:
- Rust-CPython - a set of bindings in Rust for the CPython runtime
- PyO3 - a basic way to write Rust software with bindings to Python in both directions.
- Snaek - lets developers create Rust libraries that are loaded dynamically into Python as needed, but don't rely on being linked statically against Python's runtime.
- Cookiecutter PyPackage Rust Cross-Platform Publish - simplifies the process of bundling Rust binaries with a Python library.
Will you rust faggots give it up. Nobody will ever use rust.
And wake me up when Rust stop being a cult and becomes an actually useful language.
We actually need to ditch people that cannot handle C. Go be a "business coder" but stay away from real programs.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
As C has been constantly in the top 3 languages that coder positions are offered for and C does not tie you to a SJW infected cult, this is not even a valid comparison. Rust is a hype-du-jour, with its proponents blind to its shortcomings. They are retards that still think coding is all about the language you do it in (which is about as far from the truth as you can get, and which has been known to smart people for something like half a century) and Rust is their chosen deity that can do no wrong.
When Mozilla collapses, Rust will be gone as well. It really has not many things to recommend it, but some major shortcomings including the rabid and insane Rust community.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
Python and Perl would have never made it, if people filtered by that logic.
Programming languages don't need a huge company backing them up, as long as there is enough of a community. If Rust folks are as zealous as the Ruby folks were during the Rails era, we will have a neat C++ replacement.
I have not used Rust yet and have even been critical (as in, just add those semantics to C++ somehow and don't create a whole new replacement) of it. But the community does seem to be building momentum.
A peek at module counts
http://www.modulecounts.com/
shows that the Rust community is quite active. They are not merely evangelizing it, but rapidly building value. It does not look like Mozilla is significantly driving it on the module front. It only has half the modules as Go (which is impressive for a zero-cost abstraction language compared to a language that is high level application language), but the modules seem to be accumulating at more than twice the speed now. Modules make the language.
I wish Nim had that kind of momentum though. That is a language better aligned for my purposes.
You're part of the problem we face today. Computers are order of magnitude faster than 20 years ago and yet software still never runs any faster. Web pages still render as quick today as they did in 1997. Software still has loading screens and even with an SSD we have to wait for the operating system to boot up and settle down.
Only the State obtains its revenue by coercion. - Murray Rothbard
This is what happens when developers make business decisions. Seriously, why is Mozilla focused on promoting/using/developing Rust, when they could be focused on making their browser suck less? Probably because they have no business concerns, at all, about making a viable product (or company.) I spent two weeks exclusively using Firefox, right when Google was found to be recording everything I said, in the event I happened to say "OK Google" without a way to turn this off. After two weeks, I realized I'd rather be bugged than use Firefox any longer.
This is exactly what Joel Spolsky wrote about, when Netscape did a complete rewrite here, or in his awesome book Joel on Software . Netscape focused on a rewrite, instead of making their browser suck less.
It sounds like Netscape made this mistake and then became Firefox. Now, it seems like Firefox is making the exact same mistake. This has to be the funniest business case study ever.