17 ms·
”We’ll just rewrite that microservice from scratch and the error probably goes away. Preferably with the newest framework du jour”
by nikanj 5y ago
”We’ll just rewrite that microservice from scratch and the error probably goes away. Preferably with the newest framework du jour”
- bdavis__ 5y ago2021, State of the Practice. well except for using Rust, and a bunch of dependencies from the web, version determined when downloaded at compile time.
- Macha 5y agoTo be fair, Cargo defaults to using lockfiles, so you'd have to go out of your way to hit both your points at the same time.
- bdavis__ 5y agovery true, some hyperbole to make a point. "lack of newness" is a characteristic many will expend untold hours to extinguish. to my perspective, the "rewrite it in Rust crowd" is the peak; all non-Rust code is soiled, and worthy of replacement. (it is very possible that the "rewrite in Rust" movement is just a guerrilla marketing project)
- selfhoster11 5y agoI don't really care for Rust, but all non-memory safe code could benefit from being replaced. This does, for some people, mean rewriting it in Rust because C and C++ make it harder to achieve the goal of memory safety.
- politician 5y agoNot to totally discount your point, but consider that rewriting is a form of study.