Hacker News new | past | comments | ask | show | jobs | submit login

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.




I to have written a service that still runs and never touched it’s code since. I think I used COBOL.


Interestingly, Graydon has mentioned in the past that he may have named the language after the fungi.


Never touched code is seldom a sign of quality. But there's the old saying; if it ain't broken, don't fix it.


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.


When code is never touched, it's usually because its business requirements don't change.


Or everyone is too afraid to touch it.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: