News for hackers. Stuff that matters.
Re:Case Study: Npm uses Rust for its CPU-bound bottlenecks [... by fpgaminer on Sunday March 03, 2019 @02:30PM (#19296305)
I wrote and deployed a production service written in pre-1.0 Rust. In over three years of being deployed I never once had to touch that code. The infrastructure around it evolved several times, we even moved cloud providers in that time, but that particular service didn't need any changes or maintenance. It just kept chugging along.

Perhaps Rust's name is apropos: your code will be so reliable that you won't need to look at it again until it has collected rust on its thick iron framework.

Re:Case Study: Npm uses Rust for its CPU-bound bottlenecks [... by itiman on Sunday March 03, 2019 @03:11PM (#19296528)
I to have written a service that still runs and never touched it’s code since. I think I used COBOL.
Re:Case Study: Npm uses Rust for its CPU-bound bottlenecks [... by saagarjha on Sunday March 03, 2019 @03:24PM (#19296603)
Interestingly, Graydon has mentioned in the past that he may have named the language after the fungi.
Re:Case Study: Npm uses Rust for its CPU-bound bottlenecks [... by z3t4 on Sunday March 03, 2019 @03:00PM (#19296464)
Never touched code is seldom a sign of quality. But there's the old saying; if it ain't broken, don't fix it.
Re:Case Study: Npm uses Rust for its CPU-bound bottlenecks [... by todd3834 on Sunday March 03, 2019 @03:19PM (#19296575)
Another saying, “broken gets fixed but shoddy lasts forever”.

Edit: this seems like I’m suggesting rust makes shoddy results. Didn’t mean to imply that. I’m actually very excited to use Rust in prod soon.

Re:Case Study: Npm uses Rust for its CPU-bound bottlenecks [... by majewsky on Monday March 04, 2019 @04:49AM (#19300031)
When code is never touched, it's usually because its business requirements don't change.
Re:Case Study: Npm uses Rust for its CPU-bound bottlenecks [... by z3t4 on Monday March 04, 2019 @06:50AM (#19300547)
Or everyone is too afraid to touch it.