> So this isn't the approach I'd recommend for this kind of project, but we started fresh from scratch.
wow, the from scratch rewrite. I can't even imagine that for a major piece of software
wow, the from scratch rewrite. I can't even imagine that for a major piece of software
https://www.influxdata.com/blog/rust-can-be-difficult-to-lea...
The rewrite started in 2020... they rationalize now, but it's pretty clear they just really wanted Rust and found the reasons they list later as a post-decision justification. Nothing wrong with that, if you don't mind risking the future of your business on a risky rewrite... though if I had a job working on the Go code base and my employer suddenly announced we should drop everything and start a rewrite, so go learn Rust, which has a much smaller job pool in my area as far as I can see, I guess I would've been really pissed off and would leave as fast as possible.
It wasn't until late last year that we made the decision to go all in on the rewrite and made that the focus of everyone in engineering. And we did that because we had 4 years of experience trying to get v2 and Flux to be successful, with modest results.
Most of the time we were developing this version, we were spending massively more engineering effort on developing v2 or maintaining v1 for our customers.
Using rust for any other reason than its the best option technically, is just fad chasing.
How does learning Rust reduce your chances of getting a new job? Learning new stuff increases your chances, not decreasea them.