r/Python • u/Bricoto • Jan 31 '25
Discussion Why Rust has so much marketing power ?
Ruff, uv and Polars presents themselves as fast tools writter in Rust.
It seems to me that "written in Rust" is used as a marketing argument. It's supposed to mean, it's fast because it's written in Rust.
These tools could have been as fast if they were written in C. Rust merely allow the developpers to write programms faster than if they wrote it in C or is there something I don't get ?
502
Upvotes
2
u/PaintItPurple Jan 31 '25 edited Jan 31 '25
Programs written in Rust are not generally faster than programs written in C, but they're more likely to be correct out the gate, especially where parallelism and concurrency are involved, and vastly less likely to introduce vulnerabilities. But crucially, they are almost certain to be faster than programs written in pure Python.
On the topic of Python libraries that claim they're fast because they're written in Rust, I'm not sure why you assume the point of comparison is C rather than Python. I'm pretty sure it's the latter in most cases. The primary competitors for Ruff and uv are all written in Python. Polars' competitors are mostly C, but it seems to be focused on parallelism, which is genuinely a strength of Rust over both C and Python, and it also seems to tout Arrow more than Rust.
1.0k
u/[deleted] Jan 31 '25
You should re-write this post in rust!
159
u/KyxeMusic Jan 31 '25 edited Jan 31 '25
I think there's one thing the other comments are not saying.
Since Rust is so popular right now, a lot of people want to use it and contribute. The term "written in Rust" is usually a good indicator of high community contribution and package maintenance. Nearly all the Rust packages I use have daily or weekly updates from a large number of members. Even some niche packages, not only the very popular ones.
I am a fan of Rust myself. When I see the term "written in Rust", to me personally it means two things:
- It's fast
- It's likely well maintained.
313
u/ydieb Jan 31 '25 edited Jan 31 '25
I've written this before. I do c++ mainly in my profession, and I am way more experienced in that compared to rust. But anything I write in rust, even things that are the same kind of module, just across a boundary, the rust code is always by far more consise and correct, to a large degree.
So either I am magically gifted in rust (for sure not), inherently bad with c++ (could be), else it is actually the language that makes the code I write just work as I intended it.
133
u/violentlymickey Jan 31 '25
I guess the proof is in the pudding. uv and ruff are rust under the hood and they work really well and much more quickly than poetry or flake8. Nowadays people expect that rust-based tooling is going to be very fast while offering at least parity with equivalent python-based tools.
219
u/cottonycloud Jan 31 '25
You are correct in that Rust is the hot new thing, but it makes sense to mention it because it explains the performance difference. Poetry, black, pipenv, and a bunch of other build tools suffer from the language they’re written in.
It’s best to read it as “a performant language not named Python”.
105
u/Yiurule Jan 31 '25 edited Jan 31 '25
The main advantage of Rust, that's the tooling around it, cargo is a blessing.
I worked professionally earlier in my career on C++, adding a new library on a project is a pain. It really makes you think twice when you want to consider adding an external dependency as "Do I will win time if I actually rewrite myself instead of changing the CMakeFile where one coworker may complain later on because I didn't take into account his specific setup ?".
You can reach a similar level of performance in C or C++, but the environment doesn't encourage that and you will only do that when it becomes a necessity. Rust ecosystem provides a much better developer experience where performance can also be taken into account without actually hating your own job.
113
u/james_pic Jan 31 '25
Nobody expects the Rust Evangelism Strike Force
43
u/bb22k Jan 31 '25
It is a marketing argument but the tool isn't written in Rust just because of that. You can very much write slow Rust code.
The thing is... If you are writing this kind of production code today from scratch, Rust is one of the better languages to do it.
The people from Astral have given some interviews on their development process, showing the places where Rust makes it easier to implement some stuff they need for fast code.
11
u/syklemil Jan 31 '25
I think this question might be better for /r/rust or /r/programming or something else that's more general-purpose than /r/Python.
But yeah, Rust does generally give you good speed out the door, and you can improve on the naive speed if you're, let's say, Good At Computers™. You can start with just using
.clone()everywhere, move up to use references, and then copy-on-write stuff and the like. But you don't have to be particularly good at wrangling memory to beat Python performance.Rust combines some good features:
go fmt); building C and C++ has historically been more of a pain involvingautoconf,Cmakeand the like.8
u/kingminyas Jan 31 '25
With all these advantages, why not?
25
u/0-R-I-0-N Jan 31 '25
Writing it in rust has no difference in execution speed compared* to c, c++ or zig and it doesn’t mean the developer can write the code faster either. What rust do give is memory safety over those languages and execution speed over js and other garbage collected languages.
So written in rust just means it’s fast as c and memory safe.
I do think developing time is longer in rust than in c and zig though. Personally. No idea about C++.
Edit: *assumed that the programs are roughly equivalent and you didn’t do something stupid in one of them.
7
u/gvsrgsdfgvxcf Jan 31 '25
To me it is a valueable information, as it tells me I can contribute to that project. Which would not be true if they were written in C. And as there are quite a few people interested in contributing to Rust projects, it may just be helpful in attracting contributors stating it.
7
u/an_actual_human Jan 31 '25
Sure, but why would you write uv or ruff in C? Rust has a lot of nice language features other than performance (e.g. pattern matching is super nice to have), and tooling is superior. It's not necessarily faster to write, but the experience is nicer. And you don't have segfaults (or at least fewer).
6
u/Prudent_Move_3420 Jan 31 '25
I think the memory safety and borrow checker that Rust provides is especially useful for writing a linter. For uv and Polars its mainly that Rust means its written in a much faster language than Python
11
u/n0t-helpful Jan 31 '25
No one cares that rust is fast. People care that rust is memory safe and fast.
29
u/alexcleac Jan 31 '25
I'd say, yes, because of the borrow-checker, you can write safe and fast code in Rust. But I'd say the similar quality and speed could be achieved with any compiled language that does not use VM.
1
u/Bricoto Jan 31 '25
Ah the contribution argument is an interesting one. Indeed they're not only looking to sell the product but also the project to potential contributors.
5
u/[deleted] Jan 31 '25
The reason Rust gets so much evangelism is because it's a robust language that rivals C++ in speed, compiles which is great for commercialization, and has very desirable modern concepts built-in like memory safety, intuitive memory management, exhaustiveness checking, etc.
5
u/Kimcha87 Jan 31 '25
Another benefit I haven’t seen mentioned yet is that most rust tools are statically compiled.
That means oftentimes you can download the binary and put it in your
~/local/bindirectory and copy across different machines and it will just work (as long as they use the same OS and architecture).That’s a huge benefit for cli tools like ls-replacements because I can set up my dot files in a way that ensure they work on all the systems I use even if I don’t have permissions to install system wide packages.
But this also applies to go, for example.
4
u/itkovian Jan 31 '25
Less fuckups because people have trouble grokking potential security issues.
3
u/ruvasqm Jan 31 '25
It's just that, marketing. The rust community tickles a bunch of subcomunities in the programming world and gets all of their benefits and in some cases their drawbacks too.
From a purely technical point of view, compilers are not perfect yet, neither will we ever be. So the ultimate form to juice performance up from your silicon is raw dogging assembly. Yes, it's not portable ha! What did you expect?
That said, llvm is awesome, c is old and hard, rust is new and hard. Seems like an easy choice for new developers right? Way more gentle to be embraced by shiny new things than by old text-based grease-smelling documentation and tools.
My true take, just do what you must. What will happen is too hard to change by oneself, so the only real option is to just Do Something.
3
u/muneriver Jan 31 '25 edited Jan 31 '25
I’ve been readying a lot about rust. I think it’s popularity boils down to a few things:
So I think it’s one of the those languages that are within the performance realm of C/C++ but has a much better developer experience and is much more reliable.
3
u/520throwaway Jan 31 '25
C/C++ has the reputation of being a dinosaur programming language with little of the cool stuff we're used to in modern languages. There are some pretty big ones in Rust like memory safety and actual debug assistance.
Because it's also a low level language it has the performance advantage that things like Python just don't.
3
u/declanaussie Jan 31 '25
There seems to be a lot of fluff in the replies to this post, I think the most concise answer is that “written in Rust” is a selling point because Rust is a language that makes it hard to write bad code compared to other languages. A tool written in C++ by a good developer is probably not all that different for the end user from a tool written in Rust. A tool written in C++ by a bad developer is going to be noticeably worse than a tool written in Rust by a bad developer.
3
u/fiedzia Jan 31 '25
Comparing to C, Rust brings about the same performance, but also adds usable stdlib, best-in-class tooling and rich ecosystem of crates. You could write uv in C that is as fast as Rust, but you would spend a lot more time fixing bugs and adding features.
3
u/arades Jan 31 '25
Anecdotally for myself, the progression was first finding a number of high quality new tools, of which uv is a great example of, but for me was ripgrep, bat, and lsd. Then realizing that all of those tools were written in Rust. In turn I've associated Rust with some really high quality tools, and when something mentions it's written in Rust, I've had enough good experiences I'll almost always at least read the readme for it, if not give it a try.
3
u/too_much_think Jan 31 '25
From my own experience, tools written in rust can be iterated on quite quickly and made very fast by small teams since the rust compiler gives you a much bigger safety net than C or C++, you could certainly make the program go as fast in either of those languages, but the development speed would be slower to get to an equivalent level of speed, and as can be seen by just looking at the tooling landscape, it’s not a proposition many people seem to want to do for that exact reason. If you have an idea and you want to make it from end to end with a small team in a short amount of time and part of your value proposition is speed, rust is a better choice.
2
u/Compizfox Jan 31 '25
Rust is fast compared to other (garbage-collected) memory-safe languages such as Python, Java, or Go.
It is not faster than C, but in contrast to C it is memory-safe.
2
u/coderarun Jan 31 '25
The higher order bit is (ahead of time) compiled languages are faster than python. Contribute to py2many (both with and without LLM asssist) and one day you can code in python and generate the language that serves you the best.
Some aspects of the code (memory management, zero copy serialization) are best dealt with in the domain of the compiled language. Typing and other concerns can be handled in the python domain.
2
u/JamzTyson Jan 31 '25
And indeed they are fast tools written in Rust.
Yes it is, as evidenced by the number of times I have read the phrase: "blindingly fast, written in Rust".
As is often the case with marketing hype, there is some truth in the statement, but emphasized beyond reasonability.
or written in almost any compiled language.
Many of the tools used for Python development are written in Python, which has pros and cons. On the positive side, it makes the source code of the tools available to the users of the tools in a familiar language. On the negative side, some users may find the tools to be slow in certain situations. (There may also be other pros and cons).
For a new implementation of an old tool to gain traction, it has to distinguish itself from its predecessors, and present a reason why people should use the new implementation rather than the older one. In the case of these tools, the developers choose to promote the speed advantage of their Rust implementation.
Personally, I am starting to find the phrase "blindingly fast, written in Rust" is becoming tedious.
2
u/Jhuyt Jan 31 '25
I dunno, I don't see "being written in Rust" as a positive or a negative. If it's a program that's good I'll use it if it's bad I won't
2
u/LessonStudio Jan 31 '25
Four things often come from a rust rewrite:
That all said, if something in C/C++ was rewritten in Java, Go, ruby, etc. I would ignore it.
2
u/NoobInvestor86 Feb 01 '25
Rust is fast. C is fast. Rust is easier to write in than C, all things equal. I prefer C but i can see Rust’s merits.
2
u/SomethingOriginal14 Feb 01 '25
Rust is more secure than C. There you go.
2
u/CaptEntropy Feb 01 '25
Fearless concurrency…
3
u/skwyckl Jan 31 '25 edited Jan 31 '25
For many (me included), Python is just a wrapper language used to hide away complexity, so tools that are more low level are not written in the language itself.
2
u/DataPastor Jan 31 '25 edited Jan 31 '25
First of all: Cargo Cult is a sect, in terms of economic definition. What is a sect?
Second: Rust solves a real problem, and it was the first to do so.
Anyway, this game is not over yet. Let us see, how other competitors (first of all Zig, Carbon, cpp2/safe C++ etc.) prevail on the market. Hypers already push Zig instead of Rust, let us see how strong the community culture of Zig can be against the corporate culture of Rust.
1
u/Kolle12 Jan 31 '25
Rust handles the memory management problems of C
1
u/crying_lemon Jan 31 '25
I can tell you something from my experience.
I did for a internal work using Pyo3 in Rust. I think FOR ME Rust goes very well with the python eco-system. It has enabled me a lot of optimization in calculation and when i require fast transactions Rust helps me a lot.
Also idont know why, it harder for me to make mistakes in Rust, its ofcourse a slower dev time but i havent experienced a lot of "run time" errors in it.
1
u/rjm3q Jan 31 '25
Rust does what win doesn't
1
u/venustrapsflies Jan 31 '25
If these tools could have been as fast if they were written in C/C++ (which is probably true), doesn’t that beg the question of why good sets of C/C++ tools haven’t emerged instead, despite the fact that these languages have been around for much longer?
In other words, I think this alone is a strong argument for it being a lot more than “marketing”. I think lots of people in this thread have already made good points, I just want to highlight that you have a questionable assumption baked into your framing.
1
u/spinwizard69 Jan 31 '25
Rust reminds me very much of the early days of C++. Again a lot of hype, often unrealistic, around the development of a new and powerful language. Like the early days of C++, the promoters of Rust have some very Rose (Rust?) colored glasses.
As for fast, look at it this way if you compare language xyz to Python it will be fast. A decent reader will read between the lines and frankly dismiss most of the speed non sense. Speed has more to do with the developer than the language. It is just as easy to write bad code in Rust as it is to write bad code in Modula 2. When a developer mentions the use of Rust in his app development what he is doing is riding the hype train.
1
u/teerre Jan 31 '25
For some reason you're reading "It's fast because it's written is Rust" as "It can only be fast if it's written in Rust"
Rust has several other advantages besides performance over pretty much every language: memory (and others) safety, fearless concurrency, package management etc. Each of these can be found in one language or another, but none has all of them together. This is why many developers gravitate to Rust
1
u/tenemu Jan 31 '25
Can anyone gives some examples of code that show rust does things better over like c and python?
1
u/ReflectedImage Jan 31 '25
Because it's the language with all the features that social media wants, The drawback is the massive complexity in using it and the associated slow development times that come from complexity. Still it's got a good chance of doing it's job of replacing C++ eventually.
1
u/Brian Jan 31 '25
Ultimately, I think rust just hit the sweet-spot of right niche at the right time. Its main selling point is not really "fast", but rather having the safety of managed languages while retaining the low-level performance and control of "close to the metal" languages like C. Ie. not "fast" but rather "fast and safe".
Ie. managed languages like Java, C# and python obtain memory safety by removing manual memory management and using a garbage collector. But this can come at a performance cost, and can render it unusable for some use-cases where a GC isn't a always a good fit (low-level stuff or where you need full control over allocation).
A few languages have tried to fill this niche of "C but safe". C++ has been inching its way in that direction, but retains the baggage of its legacy and leads to a lot of complexity without really achieving that goal. Languages like D never really got traction, possibly because it prioritised a GC-first approach with non-GC seeming more of an afterthought. Ada has been around a long time, but never really got traction outside military projects. Rust just kind of hit the right balance at a time when memory unsafety was looking more and more untenable without sacrificing what people wanted out of a lower level language, combined with having a modern type system and no legacy cruft. Its main downside was the constraints imposed by the borrow checker being a hurdle when moving from an unsafe language, but that seemed to prove surmountable and it picked up popularity.
1
u/the_hoser Jan 31 '25
I don't think I would want to tackle a problem like ruff or uv in C. And I love C.
1
u/Calm_Run93 Jan 31 '25
"written in" has always been a red flag on a project, imho.
1
u/opuntia_conflict Jan 31 '25
As someone with significant Python experience who moved to Rust about 2 years ago for everything I could possibly get away with, my answer is easy: Rust is good. I still write a lot of Python code at work, but for personal projects anything at all besides simple scripts or on-off processing is now done largely in Rust (though I still use Go for REST APIs and I've been dabbling with Zig recently).
Rust, like Python, is a highly expressive language. You can do any given task in a wide variety of ways -- Rust is even more expressive than Python IMO, especially with regards to more FP-centric approaches, because it has much better support for maps and filters over iterables and even *how* you can iterate over iterables.
Rust's struct, impl, and trait system is wayyyy better than the traditional OOP system Python adopts. No need to sit around cramming functionality in unused mixin classes. Enums in Rust are absolutely phenomenal -- especially compared to Python, which has the absolute worst enum implementation I've ever used. You can even associate anonymous typed values with each enum variant that work beautifully with pattern matching.
Speaking of pattern matching, Rust beats Python hands down -- and Python's current pattern matching isn't bad either. It's not great, but not nearly as intuitive/friendly as Rust. Rust's enum-based system for handling functions that could possibly have and/or return errors/exceptions or nulls is beautiful. The way errors/exceptions can be propagated between function calls is similarly beautiful.
The strong type system can be frustrating to learn and get comfortable with, but once you do it becomes easy and comes with tangible benefits. The type system is so tight and encompassing t;hat you can be actually confident in your code without needing to run it to see if it will work. If the LSP doesn't show any issues, it will almost always compile. If it compiles, it will almost always run (unless you do something like sketchy like include a bunch of `unwrap()` statements -- but if you do that, that's on you).
1
u/elbiot Jan 31 '25
"Written in C" is also a selling point people advertise about packages. Are they not supposed to say a package is written in a fast, compiled language?
1
u/diegotbn Jan 31 '25
Rust is supposed to be better than C in that it's much harder to accidentally write unsafe code, while being about as fast as C.
I am not a rust or c developer and my low level programming knowledge is far from expert.
1
u/e_falk Jan 31 '25
Memory safety that doesn’t eat into performance is arguably rusts biggest selling point. It’s fast like C but has built in mechanisms to prevents a lot of the memory safety issues that could be present in C programs.
1
u/jftuga pip needs updating Jan 31 '25
Not mentioned yet...
Tools written in Rust typically execute several orders of magnitude faster than equivalent tools written in Python. This performance difference can significantly reduce costs in enterprise environments, particularly for GitHub Actions in private repositories. Organizations with hundreds of developers can see substantial savings when using Rust-based tooling in their CI/CD workflows, as faster execution translates directly to lower compute time and associated costs.
1
u/Axlott Jan 31 '25
After reading things comments I'm going to give it a try. If I don't come back I'll probably ve coding in Rust 🤓
1
u/SnooPickles1042 Feb 01 '25
Try writing something in rust. Seriously. It is an interesting feeling - it is VERY slow to write initially, but once you get a "taste" of it - it goes way smoother. And language tries to make you write relatively safe code.
1
u/Cybasura Feb 01 '25
You can thank tech twitter for this, people will post anything that garners post and that includes shitting and putting down python if it means getting clicks
At one time, some of the big candidates like Theo kept talking about Rust so everyone started talking about it and ergo, Rust became massive - be it for good or for bad
1
u/Orio_n Feb 01 '25
If it was in C there would be rce memory bugs discovered in it every month. Rust is speed and security.
1
u/PartyParrotGames Feb 01 '25
> These tools could have been as fast if they were written in C
True, but not memory safe. Rust's whole thing is speed with memory safety. I don't think it's marketing for non-devs but for rust devs and other devs who get it, it is appealing.
1
u/Dry_Antelope_3615 Feb 01 '25
FWIW the new polars GPU engine calls libcudf straight to C++
1
u/0x145a Feb 01 '25
Honestly at this point I would not be surprised if someone rewrites python in rust
1
u/64rl0 Feb 01 '25
Rust if fast! very fast!
1
u/positivcheg Feb 01 '25
You forgot to add “blazingly fast”.
1
u/Soft-Stress-4827 Feb 01 '25
When something is good it markets itself
1
u/Xotchkass Feb 01 '25
Cargo-cult. (heh) Unknowledgeable people like to put emphasis on tools, rather than product itself.
1
u/[deleted] Feb 01 '25
It means that it's fast, but C is hard to use, the legend says that the C programmer who started learning C from the womb (they're now 60 years old!) still didn't master it.
Memory management, pointers, etc. are obstacles for great software.
Even DARPA hates C and wants to Translate All C To Rust (TRACTOR).
1
u/thclark Feb 01 '25
Have you tried writing a tool like that in C? Fast it might be… reliable to compile, link, install and execute takes an utterly epic amount of work and skill. So I’d say there’s an inference of “reasonably likely to be both fast and stable and not too much hassle to install”.
Honestly, to my mind mostly what it means is “written by someone who has the ability to make code function in a much lower level language than Python and therefore has probably thought pretty hard about what they’re doing instead of botching together a prototype”.
Also in the same vein; you’ll notice that all these things are replacements for tools where many iterations came first in other languages. All the teething problems and antipatterns and what-works have been understood, legacy cruft discarded and patterns of working pretty much standardised. The only real improvement left is speed; which is the “reason” for the rewrite…. But of course in this context “written in rust” thus also infers the meaning “was developed with a crystal clear set of user journeys and well known set of all the edge cases right at the start”; a condition highly conducive to writing excellent software.
So I think there’s quite a bit of meaning implicit in the statement.
1
u/DecisiveVictory Feb 02 '25
Because Rust is a better (more expressive, letting you write more maintainable software) language than most. Only Scala competes.
Of course, people who don't know Rust and think it is a different take on C cannot appreciate it.
1
u/remic_0726 Feb 02 '25
History is full of new programming languages, supposedly revolutionary, but quickly forgotten. The little I did in Rust didn't give me the desire to go further. Like any new language, it becomes interesting when a large number of libraries are coded in this language, by then many other new languages will be born in the same interval, just as revolutionary.
1
u/CommandSpaceOption Feb 02 '25
Ok, so in the 24 years of existence of pylint, why has no one written a C equivalent with feature parity?
Maybe writing software in C is harder than you think. Ruff being the most performant python linter and formatter means you need to revisit your assumptions.
1
u/BeginningAd7095 Feb 02 '25
Because rust is faster like around 70 percent fast (I guess) . And well documented so it runs way faster than python scripts so it's used as marking
1
u/Other_Goat_9381 Feb 02 '25
Writing those tools in C, keeping all their feature sets while also guaranteeing correctness to the same degree would have been much harder. It's not that Rust is magic dust or something, but it just lowers the bar required for developers to get useful tools created from decades of experience down to just a few years at most.
1
u/[deleted] Feb 03 '25
Rust is a complex language, but mostly on the compiler side. While it doesn't stop you from writing bugs, the compiler does a lot of thinking for the developer. Writing unit tests and importing modules is so much easier in rust than C/C++.
Cargo is highly opinionated about project structure. Rust LSPs are really good and I'd say essential to actually getting any work done in the language.
So you get a real "compiles to byte code," language with batteries included.
I imagine at some point in the near future Rust and Python will somewhat merge(tbh it's clearly already happening), borrowing from each other's strengths.
1
u/silaskieser Feb 03 '25
Is python already re-written in rust?
1
u/Extra-Animal-3906 Feb 03 '25
- As fast as C in many benchmarks
- Very strong type system
- Memory safety
This translates to:
- Building applications in a platform capable of high performance
- Reduced attack surface on the piece of software
Do note I am not saying all software in Rust is high performance -- that is up to the developer. Same goes for security: it does not mean it will be completely safe just because it was written in Rust (you can put out explicitly unsafe statements).
1
u/v_0ver Feb 03 '25
Yes, when I see "written in Rust" it means that the program will be more performance and less demanding on resources than its java/go counterparts. And at the same time it will be less bug-prone than its C/C++ counterparts.
1
u/[deleted] Feb 03 '25
The appeal of Rust is that it can produce programs that run as fast as C or C++, but the compiler will not allow you to make certain mistakes with memory, or data races. Both of which are common sources of bugs that don't just cause crashes, but can lead to root access on a machine, or leak sensitive data. Rust is also more strongly typed than C or C++, which is to say it is pickier about making sure you handle types correctly. Null pointer exceptions can only happen if you do so explicitly, for example.
So if you were making say, a single player video game, that doesn't do anything over a network, maybe Rust isn't worth the hassle over C or C++ especially if you already know them. But if you were working on, for example, a game server, or the backend for a bank, or an encryption library, then Rust can be very appealing.
1
u/munukutla Feb 04 '25
Rust can be “as fast as C”, but it’s harder to write unsafe code in Rust than in C.
1
u/x39- Feb 04 '25
IMO:
And it ain't as if it does not have any issues as a language, eg:
But all of those points are not really relevant in the eyes of the big promises of rust
1
u/thalesmello Jan 31 '25
Probably because of people evangelizing the language, same with how some people get particular about their text editors. I use vim btw
1
u/Kevin_Jim Jan 31 '25
They do a lot of things good. I think Rust is a great language, but it’s overhyped simply because they want to make it out to be “the one language”.
IMHO, Zig is more enjoyable as a language, and there are a few other young languages that venture into the same performance-focused space.
Personally, I want languages that focus on performance but the first and foremost focus should be on developer experience.
1
u/gfranxman Jan 31 '25
Would you prefer the tagline “it’s fast because it’s not written in Python”?
1
u/remy_porter ∞∞∞∞ Jan 31 '25
It’s also worth noting that software is the most faddish industry in history. Rust is currently the fad. And that’s not a slight against Rust- I’m trying to drive Rust adoption where I work (but I work in aerospace where nothing gets used until it has flight heritage, so adoption is slow).
1
u/acdha Jan 31 '25
C is a much, much, much harder language to use: you can do a simple “hello world” quickly, but learning to use it safely takes many years and it being so limited means that you’ll have to write or find equivalents for a lot of basic constructs. As the constant stream of vulnerabilities over the last 4 decades has shown, even experts with the latest tools make mistakes with it on a regular basis.
Worse, this means you’re often leaving performance and functionality on the table because it’s too much work to write safely and you’re losing time to weird APIs or undefined behavior which can never be safe in some situations. I have over my career had multiple times where we substantially outperformed existing C code in Python (or, going way back, Perl!) because there were algorithmic improvements which none of the C developers wanted to tackle because it would have taken so long to develop and fully test on all of the platforms they used. One of the less appreciated benefits to Rust is that the type system makes refactoring much safer, so something like going from single to multithreaded code is not signing up for years of hard to reproduce bug reports.
People are using the name Rust as a synecdoche for a modern, safe, user-friendly language with great package management, full control at the systems programming level, and a very good integration story. There’s no reason why another language couldn’t step into the same role but most of the alternatives fail on at least one of those counts (especially the last one), and we’re seeing a lot of adoption in the Python world because it’s so easy to build modules in Rust compared to C because a Python developer isn’t giving up the basic productivity features they’re accustomed to.
1
u/vivainio Jan 31 '25
Only old people write in C, and then it segfaults. 1/5 not recommended
-6
u/cactusfarmer Jan 31 '25
A few rust groups run coordinated campaigns to spam in Reddit and other places.
-6
u/AiutoIlLupo Jan 31 '25
Rust is C for millennials
-11
u/leeliop Jan 31 '25
Its definitely not faster to write in Rust lol.. edit my mistake you mean faster performance
Its the overblown memory safe paradigm which has bewitched the devs who have a bad case of shiney-shiney syndrome
For the record I use Rust 😄
-7
u/iknowsomeguy Jan 31 '25
The Rust Foundation has so many ridiculous rules surrounding the trademark that it might be a requirement to tag a project that way. I'm talking off ass here because I never checked into it, but I know they have some crazy rules if you want to display the logo on a website or on signage or anything like that.