3 ms·
The SW world is full of Java/C++ rewrites of products that originally started out in a dynamic & productive language like Lisp or Python. It might make sense in
by fulafel 7y ago
The SW world is full of Java/C++ rewrites of products that originally started out in a dynamic & productive language like Lisp or Python. It might make sense in the lifecycle phase when you're past making big changes under make-or-break pressure, and are in the "provide predictable 10 year maintainance roadmap for this large codebaes" stage. You end up employing different kinds of programmers too because many of the original team may be reassigned to something more exciting/important to do.
But it's in no way inevitable, of course, there are many old Lisp, Python, etc codebases in production too.
BTW. I've been trying to rediscover this blog post and can't seem to find it again, anyone? It described different kinds of software projects, the (1) kind that try to deliver incremental improvements (eg 10% cost savings), and the (2) kind that try to make 10x improvements, and the difference in how those projects are run (the 1-type project can't go over budget because it will then deliver negative value etc).
- agumonkey 7y agoalso they can still have hybrid clojure jars if needs be
- 0815test 7y agoHopefully we'll start seeing some Rust rewrites in the future then, since the pitfalls of C++ are widely-known by now, and few people would claim that they don't impact long-term maintainability. (And the Rust Evangelism Strike Force would surely approve of such a shift!)
- geodel 7y agoIf Rust Evangelism Strike Force volunteers to rewrite code in Rust instead of heckling original developers to do it they may prove themselves to be more productive and useful.