If you hang around certain spaces of the internet (here, Reddit, etc), any sufficiently popular post about a Rust-related project is bound to accrue some comments along the lines of "Rust is actually not that great", "rewriting is bound to gain new bugs that won't be caught", "the borrow checker is practically byzantine and not worth the trouble", "C is perfectly adequate", "more advanced type systems are less useful than writing more tests", etc. I would even say that comments of this nature constituted a good chunk of the discussion around the US government's C-to-Rust initiative (a very popular post with a lot of comments).
The Rust Blowback had some reasons: People arbitrarily opening bug-tickets on various projects saying they should be Rewritten in Rust for Safety. This became a Meme.
In my experience, the majority of negative responses are rooted in fundamental misunderstandings of type systems and expressive power. The vast majority of everyday programmers are pretty much only familiar with Java or TypeScript when it comes to statically typed languages, and it can be hard to get people with that background to understand or appreciate the substantial increase in capability that systems like Rust's provide.
(The issue is further exacerbated, in my opinion, by the prevailing notion that test-driven development is superior to — or at least generally more than adequate for — anything and everything that could be desired. Years ago there was a tense Twitter exchange between Bob Martin [of "Clean Code" note] and Shriram Krishnamurthi [a prominent programming languages researcher and professor at Brown University] on this topic, Martin seemingly unwilling to move past a TDD-oriented worldview at that time.)
It's often framed as useless monkey business, rewriting working software to produce a copy of it but in another language, for questionable benefits.
I'd say that rewriting anything in any language (even in the same language) would remove large amounts of cruft, and add long-missing neat things that are easier to add when you build from scratch, and with a good understanding which the original authors lacked. Often it also can afford using a better architecture, see rg vs grep: grep has many brilliant technical solutions, but making it multithreaded would be a major rewrite anyway.
Along with everything else mentioned, there is a certain group of people who consider the language “woke”. Usually that’s not the critique you see on HN, but be wary of it.
If you hang around certain spaces of the internet (here, Reddit, etc), any sufficiently popular post about a Rust-related project is bound to accrue some comments along the lines of "Rust is actually not that great", "rewriting is bound to gain new bugs that won't be caught", "the borrow checker is practically byzantine and not worth the trouble", "C is perfectly adequate", "more advanced type systems are less useful than writing more tests", etc. I would even say that comments of this nature constituted a good chunk of the discussion around the US government's C-to-Rust initiative (a very popular post with a lot of comments).
The Rust Blowback had some reasons: People arbitrarily opening bug-tickets on various projects saying they should be Rewritten in Rust for Safety. This became a Meme.
Just like some highly publicized cases of child kidnapping led to "stranger danger."
Reasons, yes. But not very good ones and blown way out of proportion.
In my experience, the majority of negative responses are rooted in fundamental misunderstandings of type systems and expressive power. The vast majority of everyday programmers are pretty much only familiar with Java or TypeScript when it comes to statically typed languages, and it can be hard to get people with that background to understand or appreciate the substantial increase in capability that systems like Rust's provide.
(The issue is further exacerbated, in my opinion, by the prevailing notion that test-driven development is superior to — or at least generally more than adequate for — anything and everything that could be desired. Years ago there was a tense Twitter exchange between Bob Martin [of "Clean Code" note] and Shriram Krishnamurthi [a prominent programming languages researcher and professor at Brown University] on this topic, Martin seemingly unwilling to move past a TDD-oriented worldview at that time.)
Ah maybe it's an another example of people using Twitter and the conflating the brainrot on there with reality.
It's often framed as useless monkey business, rewriting working software to produce a copy of it but in another language, for questionable benefits.
I'd say that rewriting anything in any language (even in the same language) would remove large amounts of cruft, and add long-missing neat things that are easier to add when you build from scratch, and with a good understanding which the original authors lacked. Often it also can afford using a better architecture, see rg vs grep: grep has many brilliant technical solutions, but making it multithreaded would be a major rewrite anyway.
Along with everything else mentioned, there is a certain group of people who consider the language “woke”. Usually that’s not the critique you see on HN, but be wary of it.
Well that's laughable so probably not worth thinking about.