3 ms·
> For example: you might not want to use Rust because its steep learning curve means you’ll spend more time learning than delivering Related to that, it might
by qsantos 3y ago
> For example: you might not want to use Rust because its steep learning curve means you’ll spend more time learning than delivering
Related to that, it might not actually be the case: https://news.ycombinator.com/item?id=36495667 https://news.ycombinator.com/item?id=36495667. Key takeaway:
> Rumor 1: Rust takes more than 6 months to learn – Debunked !
> All survey participants are professional software developers (or a related field), employed at Google. While some of them had prior Rust experience (about 13%), most of them are coming from C/C++, Python, Java, Go, or Dart.
> Based on our studies, more than 2/3 of respondents are confident in contributing to a Rust codebase within two months or less when learning Rust. Further, a third of respondents become as productive using Rust as other languages in two months or less. Within four months, that number increased to over 50%. Anecdotally, these ramp-up numbers are in line with the time we’ve seen for developers to adopt other languages, both inside and outside of Google.
> Overall, we’ve seen no data to indicate that there is any productivity penalty for Rust relative to any other language these developers previously used at Google. This is supported by the students who take the Comprehensive Rust class: the questions asked on the second and third day show that experienced software developers can become comfortable with Rust in a very short time.
- Teckla 3y ago> All survey participants are professional software developers (or a related field), employed at Google. This is not even remotely a good representational sample of software engineers.
- dan-robertson 3y agoIt seems kinda useful to me. Like, the normal problem looks much less like ‘we took competent professionals over a long time’ and much more like ‘we took 10 undergraduates over a month or two’. If you add up employed engineers at google-like companies (by which I mean large tech companies), you’ll quickly come to hundreds of thousands, and there are plenty of other companies who hire similar people. I think Google employees are reasonably uniformly distributed across that population (that is it isn’t like the Google has the best X% of them) and I think a study of such people is more interesting to me than a study of undergraduates (or indeed a study of programming language enthusiasts). I think an unrepresentative thing about Google is that they may use C++ more than many newer tech companies, and this might help for learning that.
- escape-big-tech 3y agoThis is also my experience. I was ok in rust after using it for 2 weeks, I still had the weird issues here and there, sometimes but after just using it for as little as one month I started feeling confident enough in it where I could develop anything given enough time. Now after almost a year, there is no language i'd rather use than rust
- kohlerm 3y agoBuilds are unbelievable slow ...
- qsantos 3y agoThat's not the point from the quote, and it is actually discussed in the Google article