3 ms·
-1 for ageism. What's worse, that, or persuading a client to port their app from RoR to node.js just because it's "cool"?
by gaius 14y ago
-1 for ageism. What's worse, that, or persuading a client to port their app from RoR to node.js just because it's "cool"?
- cafebabe 14y agoThat's the correct question. The only reasons for changing a running system: 1) You run out of staff that is able to maintain the platform. 2) You run out of hardware to run the platform. 3) Both, staff and hardware costs outgrow the costs of a rebuild. And the new platforms will run into the same problems as the old ones. In the end, we just create the same solutions, but on different platforms. That's the big misconception a lot of people have about new stuff like Node.js. They think, the fundamental problems will just vanish. The big advantage of Java is the specification process and the reliability that comes with it. Yes, and that's also the reason, the Java platform is not changing as much as other platforms. But that is much better for building complex systems that have to last as long as the old ones (COBOL etc).
- wmat 14y agoI was trying to keep ageism out of the discussion. I'd argue that moving to the latest and greatest must serve a real business purpose. That purpose could be to leverage modern languages to build a more extensible, flexible, and maintainable system. Technology for technology's sake is rarely a positive proposal.
- mgkimsal 14y agoUnforunately, it still does creep in. The 'real business purpose' argument must also take in to account skills of available workers. If no one is able to be hired to maintain and extend legacy system X, you're left with * hiring workers with modern skills and backtraining them on older/legacy/custom stuff that won't do them much good in the future market, so they may balk (the smarter ones would demand a hell of a lot more money). or * converting to something more modern and perhaps somewhat future proof. The code itself might not be future proof, but the processes the business puts in place during the conversion should take in to account future conversions and upgrades as part of the requirements.