7 ms·
Rust sucks because
- chrismorgan 10y ago> LLVM's optimizer considers undefined behavior a license to kill. Of course, that only matters in unsafe code, We’re not quite there yet with defining rigorous semantics for unsafe code (there are still a couple of undefined things at present), but Rust does intend to rigorously define all behaviour. So this is a quibble which is being dealt with. (Note that there’s still the odd rustc bug involving LLVM doing something it shouldn’t, but those are just bugs. See https://github.com/rust-lang/rust/issues?q=is%3Aopen%20label%3AI-wrong%20label%3AA-LLVM https://github.com/rust-lang/rust/issues?q=is%3Aopen%20label... for a couple.) > but you need unsafe code for anything complicated. … what? Somewhere deep down in your dependencies, maybe, but for most things you really don’t need unsafe code. ---- Most of the rest of the issues are either Rust immaturity (compiler is slow, &c.) or tradeoffs that the language has made (String vs. &str). There are definitely some legitimate criticisms in it.
- hyperpape 10y ago>> but you need unsafe code for anything complicated. > … what? Somewhere deep down in your dependencies, maybe, but for most things you really don’t need unsafe code. If anyone has an account or feels like creating one, that line really should be changed to "unsafe code can't always be avoided" or "fundamental types like Vector are implemented with unsafe" or something similar.
- all2well 10y ago>fundamental types like Vector are implemented with unsafe That's kind of the point, though: Vec provides a safe interface over behavior that would otherwise be unsafe. You could as easily complain that C is fundamentally implemented in machine code without any type safety.
- hyperpape 10y agoI agree that it's not a huge problem. But it does communicate accurately where unsafe appears, unlike the existing text.
- bryanlarsen 10y agoWhile true, it's missing the forest for the trees. Rust sucks because it takes several weeks to become proficient in its use. That's a huge expense for any person or company that wants to use it. It may be worth it long term to switch to Rust, but if you fail in the short term there may be no long term to worry about. https://news.ycombinator.com/item?id=13430108 https://news.ycombinator.com/item?id=13430108
- endorphone 10y agoRust sucks because it takes several weeks to become proficient in its use. I do not intend this to be advocacy for or against Rust, but your observation is true and also indicative of a profound, self-defeating issue with this industry: Intelligent, educated developers often chose the option that gives the quickest gratification, even if it causes significant long term problems. PHP is an example. So is MongoDB (and indeed many document stores). A lot of shops ended up becoming "Microsoft shops" only because it was easy to install things from the MSDN discs. Etc. Most projects of significance encompass tens to hundreds of thousands of hours of work. A small cost upfront is usually insignificant.
- arvinsim 10y ago> I do not intend this to be advocacy for or against Rust, but your observation is true and also indicative of a profound, self-defeating issue with this industry: Intelligent, educated developers often chose the option that gives the quickest gratification, even if it causes significant long term problems. PHP is an example. So is MongoDB (and indeed many document stores). A lot of shops ended up becoming "Microsoft shops" only because it was easy to install things from the MSDN discs. Etc. It really is about tradeoffs. If developers have infinite time and money, I am pretty sure that everyone would ditch those 'ugly' languages. But we are not living in this utopia. There are time and money constraints that developers have little or no control over. > Most projects of significance encompass tens to hundreds of thousands of hours of work. A small cost upfront is usually insignificant. Unfortunately, not all those who mandate what stack to use know this
- 10y ago
- ainar-g 10y agoThe website is slow for me, so here's a cached version in case anyone needs it: https://webcache.googleusercontent.com/search?q=cache:IdCGkcAL4Z4J:https://wiki.theory.org/YourLanguageSucks+&cd=1&hl=en&ct=clnk&gl=ru&lr=lang_de%7Clang_en%7Clang_ru https://webcache.googleusercontent.com/search?q=cache:IdCGkc... "Why Rust Sucks" is at the very end.
- alimbada 10y ago> Overly terse named types and keywords that don't communicate their purpose, like Vec and Cell. I completely agree with this. This type of naming convention shouldn't even be a remote possibility in this day and age. I find it extremely difficult to read coming from mainly a C# and Java background.
- eptcyka 10y agoWere you expecting the same keywords for the same things in a different language? The original Rust designers had a goal to have all keywords be under 5 characters in length to try and make the language as small as possible. I do not think that this is an issue. But to each his own, I guess.
- indeyets 10y agoIDE Support: https://intellij-rust.github.io https://intellij-rust.github.io
- maxlybbert 10y agoI read the entries for a few other languages that I am familiar with, and found the criticisms to be shallow, misguided, and silly. I don't have any confidence that the Rust criticisms are any better.
- metalon 10y agoI thought the same, e.g. this: > There's actually a special Haskell search engine to search for anything related to Haskell, because of the funky syntax not playing nice with Google. Hoogle is so extremely convenient, it's a big plus imho
- codygman 10y agoHoogle also exists to allow users to search for functions by type signature, not mentioning that is an unfair mischaracterizes.
- abiox 10y ago> Overly terse named types and keywords that don't communicate their purpose, like Vec and Cell i'm of the opposite view here; though, i think i get where this is coming from. for me, if i look at it from a "broader timeline perspective", the length of keywords (like say "function" in JS) is mildly annoying to me. especially if they're high frequency. over time, familiarized keywords essentially "fade into the background" and afterward just occupy precious horizontal space, but provide a valuable sort of visual shaping or pattern. given this, i love the elements of terseness in rust syntax. my identifiers are what i want to be more expressive and descriptive. this combos well: terse keywords and stdlib elements contrast excellently with longer identifiers and make it easier and faster to read (for me).
- edejong 10y agoIn some of my programming environments, such as Emacs, I choose to prettify keywords to unicode characters such as 'function' (λ), 'lambda' (λ), 'forall' (∀) and others. It takes a bit getting used to, but it brings the focus where it needs to be: the code and data flow. The brain quickly adopts new pattern-matchable structures, so why bother with long keywords? [1] http://emacsredux.com/blog/2014/08/25/a-peek-at-emacs-24-dot-4-prettify-symbols-mode/ http://emacsredux.com/blog/2014/08/25/a-peek-at-emacs-24-dot...
- imron 10y agoSome things are obvious, some are not. Keywords are not really the problem, it's more when people start abbreviating their identifiers. One I saw in some codebase a while back was xxxxRec and it took me a while to realise it was an abbreviation for Receiver because for whatever reason my initial mental auto-complete was Record and that wasn't making much sense. And while it will always be obvious to the person writing the code, it might not always be obvious to the person reading the code. Sometimes that's even the same person. So I agree that Rust feels a little too heavy on abbreviations at times.
- bluejekyll 10y agoAs the IDEs for Rust becomes more powerful, the name length issue will probably go away. I get terseness, but there is a balance. I am definitely in the camp of expressive naming, as it reduces confusion. In fact, I find myself waffling on generic names as well, T is common, but when you get up to 3 or 4 generics in a function, it starts looking like more expression is needed. Though I still use single or double characters, I do think about changing my mind here.
- camus2 10y agoRust is nice and developers absolutely get why it works the way it does( to provide strong memory safety guarantees, eliminate usual bugs found in C/C++ programs). Here is the issue: A lot of developers actually like the C/C++ freedom they have even if it leads to horrible bugs as they are used to program the way they do. Others are people that don't care about memory management and are fine with GC, nil errors and race conditions.
- sumitgt 10y agoLooks like C# has one of the smallest list of complaints. :) https://wiki.theory.org/YourLanguageSucks#C.23_sucks_because https://wiki.theory.org/YourLanguageSucks#C.23_sucks_because
- discreditable 10y agoMeanwhile Javascript's is the longest! https://wiki.theory.org/YourLanguageSucks#JavaScript_sucks_because https://wiki.theory.org/YourLanguageSucks#JavaScript_sucks_b...