6 ms·
While 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 pe
by bryanlarsen 10y ago
While 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
- innocentoldguy 10y ago> 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. That's the thing though, if spending two or three weeks right now to learn Rust will save you months of technical debt and futzing around with crappy standard libraries and language weaknesses in the future, then the prudent move would be to ditch the weak language in favor of Rust, regardless of its learning curve, since the end result will be a significant net-positive. I also think this is a copout. Take Java, for instance. It was new and different when it came out in the 90s, but companies all over the map were willing not only to spend weeks learning it, but also months (or years) re-writing all their crap in Java, even though it was a dismal failure in almost every instance (e.g. Java-Netware, Java-WordPerfect, Java-VisualStudio, etc.)
- btschaegg 10y ago> That's the thing though, if spending two or three weeks right now to learn Rust will save you months of technical debt and futzing around with crappy standard libraries and language weaknesses in the future, then the prudent move would be to ditch the weak language in favor of Rust, regardless of its learning curve, since the end result will be a significant net-positive. This. There's a really good point on tradeoffs in Rich Hickey's talk on "hammock driven development": "Most developers use the word 'tradeoff' to describe parts of their software that suck." If you haven't evaluated the alternatives, it's not a tradeoff. And if you are sacrificing long term maintainability for two weeks of productivity, you most certainly haven't thought it through.
- deleted 10y ago[deleted]
- azov 10y ago> Rust sucks because it takes several weeks to become proficient in its use. Huh? It takes years before developer starts writing C++ code that does not blow up in production. Even with JavaScript or Go it takes months to start writing reasonable code (as opposed to something that just seems to work). What are you comparing it to?
- BoorishBears 10y agoI think the parent post is comparing how long it takes to reach being able to consistently write something "that just seems to work"
- moomin 10y agoYeah, but the time to compile is much shorter than that. No-one bothers with the "correct" metric, just the "compiles" one. This probably explains the popularity of interpreted languages.
- camus2 10y ago> Javascript or Go it takes months to start writing reasonable code It doesn't take months to teach oneself JavaScript or Go and actually write code with it. If it did these 2 languages would not be as successful as they are. Rust on the other hand won't compile until the learner respects Rust memory model. These aren't syntax errors or even type errors, these are "ownership errors" which are a whole new level of errors most people don't want to put up with.
- chrismorgan 10y agoI think it’s more than that, actually: Rust is complex, and it takes time to absorb that complexity. This is also the root cause for some of the other issues such as the compiler performance (it’s immature and takes longer to make fast). Something like Go is much easier and faster to become productive in—but then its ruthlessly constrained design paints it into a corner for some things. (My own experience with it is that Go can be fairly nice for writing applications in, but it’s often quite painful to write libraries in.) Really, the conclusion of the matter is that Rust isn’t for everyone, and it’s not perfect yet and will take longer to get to a given level of quality than something like Go. (If as much effort was expended on Rust and rustc performance as has been expended on JavaScript performance, whoa, that would be breathtaking.)
- panic 10y agoWould professionals in any other industry complain about a tool that took only weeks to learn? If a particular language really does help us write better software, a few weeks is a tiny amount of time to spend learning it. I think we focus too much on the experience of the people who write programs and not enough on the experience of the people who use them.
- Turing_Machine 10y agoWould professionals in any other industry complain about a tool that took only weeks to learn? The tools used in most other industries change on a time scale of decades, not months. Some of them don't change for centuries. Pencils, hammers, and frying pans don't become obsolete, while the language/framework/magic thingie of the day is almost guaranteed to do so. Maybe Rust will take over the world and last as long as C, Lisp, or FORTRAN, but that's certainly not the way to bet.
- EdiX 10y ago> Would professionals in any other industry complain about a tool that took only weeks to learn? I would guess the answer is yes. After all the new tool needs to be much better than existing tools to justify weeks of retraining. In fact, I suspect programmers are willing to put up with a lot more compared to other professionals since we do a lot of our learning in our spare time.
- Shorel 10y agoI think the initial investment and the lifetime investment are quite different. They are probably evaluating: 'So, what do I feel about learning Rust stuff for the next 10 years?'
- kazinator 10y agoThey would probably complain if there were 50 different tools (each of which taking only weeks to learn) all promising to solve the same problems in different ways, and each largely excluding the other 49.
- Koshkin 10y ago> it takes several weeks to become proficient in its use Weeks? That's nothing. It takes months, if not years, to become proficient in C++, for example. (I understand that you are talking about the training of the existing employees, but still.)
- sametmax 10y ago+1. I think people are comparing it to high level languages. Also they think knowing to write the code is the same as knowing to code in that language. It's not true at all. It's quick to be able to write C code. Being able to produce something worth being on prod however, takes month.
- leshow 10y agoStarting from scratch in any language that isn't a clone of a language you already know with slightly different syntax would take a few weeks. A few weeks seems like a good trade to me for the safety rust provides for a lot of applications.
- lhinds 10y agoI did spend a shortime learning rust, and found Cargo really nice, but in the end I weighed up my time investment vs what benefits I would get from rust. I ended up sticking with Golang and Python. This decision was made, because the sort of apps I work on (OpenStack / Kubernetes / DevOps type workloads) have no need for the zero cost performance that Rust brings. If I was building applications where performance is key (such as networking, Kernel, OS libraries etc), Rust would be great for me. But currently Go gives me enough speed and is far easier to make progress in (with the time I have available). Rust has a great community, that was a key take I tool from my time there as a newcomer.
- grzm 10y agoWhat are your estimates for the time it takes to become proficient in their use? What's your criteria for proficient?
- sitkack 10y agoEach team and project will require a subset of the services offered (language, libraries, runtime, etc). One does not need to use the whole language to be productive in the whole language. People claim that they are quickly productive in Golang, one can also be productive in Rust in a similar amount of time. Satisfy the borrow checker with .clone and .copy. The end result will be the same. Using something doesn't mean that you are required to explore the full depth and breadth of it.