Login to reply
Replies (18)
There is no problem. They just take a solution and make a solution-rs :)
Not sure I get the Rust one
What about Kotlin?
import solver
Where is vibe coding π
Java: problem -> com.corp.foo.bar...solution
Problem -> DSL -> Problem { }
Rewrite the solution in rust! solution.rs!
Infelizmente Bitcoin don't fix it kkkk
Problem -> AbstractProblemFactory -> SolutionBuilder -> Solution
Still a good thing that a lot of c and c++ is getting rewritten in Rust.
At this point C++ -> Rust makes more sense than C -> Rust for long term maintenance.
The implication being most things written in C are "legacy", and destined to be completely replaced anyway?
No. The implication is that C -> Rust makes the codebase of that solution much more complicated/uncertain than it needs to be.
The Rust language is just not stable enough to make sure the new code will last longer than the C counterpart as the language itself evolves.
And because Rust will always be slower than C due to the additional memory checks added by the compiler in every safe access, it makes the stability/security the main benefit from the conversion (as opposed to performance gains)
So Rust, is always the solution?π€‘
What about Java?
C is and always has been double plus good.
Uh, Wait...
Haskell: Problem -> Existence proof of solution