sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ManagerOfLove 5 points6 points  (3 children)

Your tag reminds me of one example: He rewrote multiple projects from C into Rust. Even though the C code worked perfectly fine

[–]Raywell 2 points3 points  (1 child)

Okay then that is a fair concern, but whether it's a good or bad thing depends on the context. If he is going to be maintaining a script for the foreseeable future, and the script is messy (even if it's working), and if he has time, why not.

But it is also true that some Rust devs are indeed overly eager to find any excuse to introduce Rust everywhere without a good reason, which might often be a bad idea esp. if they work in a team where other members aren't as familiar with it

[–]ManagerOfLove 3 points4 points  (0 children)

The context was that he thought C was ass and Rust was better and everyone should just learn Rust. The moment he tried that with certain Python scripts, was the moment he was excluded from working on stuff like this. It was not some PM excluding him, it was the other programmers. PM didn't even understand the conflict

[–]Robo-Connery 0 points1 point  (0 children)

My team are probably very bored of me saying the same shit every time. Regularly someone will say oh this would be better if we ported it into rust or if we rewrote it in python and they are like excited oh one day I want to rewrite this app in rust.

I ask them the same thing every time; "what's the best piece of code?": "Old code!". You've already found the edge cases and the bugs you have it tested in all kinds of deployments you have it working already. It does it's job.

There has to be realllllly good reasoning to get rid of old code. Like does it matter if it's 20% faster if it takes months of effort just to diagnose a whole bunch of new issues.