Programming

13481 readers

10 users here now

All things programming and coding related. Subcommunity of Technology.

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

[email protected]

Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022 (opensource.googleblog.com)

submitted 2 years ago by [email protected] to c/[email protected]

3 comments fedilink hide all child comments

Rust adoption at Google:

over 1,000 Google developers ... have authored and committed Rust code as some part of their work in 2022

The learning curve might not be as steep as often said:

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

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 2 years ago* (last edited 2 years ago)

Two thirds being confident to work in Rust within two months of learning it doesn't sound particular fast, tbh.

In our company we're currently transitioning from old-school Java to Google's Dart (plus the Flutter framework), team by team. You get one to three days to set up the environment, reading and doing some codelabs, a course of two days and then you start developing in the decently big Dart codebase the other teams already prepared, starting your daily development business. (A second two-day course follows some weeks later). Well, nobody (systematically) asks if you're feeling confident to contribute in Dart, but it obviously works and I haven't heard any "I can't get my head around this" type of complaints.
Sure, maybe going from Java to Dart isn't that much of a change as going from whatever these 1000 folks at Google came from to Rust, but if one third of the developers does not feel confident to develop in Rust after two months of learning it, this sounds like a lot to me.