1 Like
They always make it seem quite scary 
For new teams
- First decide if you actually want to use Rust. Are you going to benefit from type safety and performance? Awesome. Are you primarily a front-end shop with an IO-bound workload that will perform roughly the same regardless? Maybe you’re better off with a garbage collected language like Go, Java or Kotlin.
- Accept that there’ll be ramp up time. Regardless of what people tell you, a language like Rust takes considerable time to become productive in. Ensure you already have some experts on the team who can help ramp others up rather than slowing down the whole team simultaneously. We have seen projects go poorly when there wasn’t an existing level of Rust expertise to serve as a guide.
- Decide how many languages you’ll have and own the responsibility of supporting them for a long time. Be cognizant of the overhead in maintaining libraries and operational systems in multiple languages.
- Be willing to say no. Sometimes the right solution is just to make-do with what you’ve already got.
2 Likes
Lol, it’s like jumping from something like javascript or java to a language where you have to actually think about the hardware at times, because that’s what it actually is. ^.^
1 Like