3 ms·
We acquired a product last year, where the entire back-end was written in Rust. Unfortunately, Rust developers were hard to get by, and we didn't have any inte
by TrackerFF 3y ago
We acquired a product last year, where the entire back-end was written in Rust.
Unfortunately, Rust developers were hard to get by, and we didn't have any internally that could maintain the Rust code at such scale.
The entire back-end ended up being re-written.
- codetrotter 3y agoNooo :'(
- beeboobaa 3y agoWhat happened to the developers who wrote the back-end in the first place?
- cerved 3y agomaybe the borrow checker determined their lifetime was up
- ducktective 3y ago>The entire back-end ended up being re-written. In Go, I presume?
- rowanG077 3y agoWhy not just learn rust? It really is not that exotic to learn. I doubt it is faster to rewrite it.
- jonnytran 3y agoYeah, this is just baffling. A team can be so averse to learning new tools, good ones too, that they would rather dump their time into rewriting. Instead of getting paid to level up their skills, they'd rather block forward movement of the company's goals to maintain the status quo.
- kasajian 3y agoI'm a bit surprised at this, too.
- shdh 3y agoTrash build times and slow iteration cycle as a result
- rowanG077 3y agoBuild times are pretty good in rust compared to most languages. Where do you get they are trash?
- imetatroll 3y agoI honestly wish I could have been in that boat because I crave the opportunity to use rust on the job.
- tracker1 3y agoSame here... Job hunting right now and would love to bridge the gap to primarily using Rust