3 ms·
So there's run-of-the-mill old code that's accumulated a lot of cruft, is hard to get acquainted with, and can be tedious to work with. But it works, and doesn'
by PeCaN 10y ago
So there's run-of-the-mill old code that's accumulated a lot of cruft, is hard to get acquainted with, and can be tedious to work with. But it works, and doesn't get replaced.
Then there's old code that barely worked when it was new and is held together by duct tape. Often it's written in something antiquated like VB6 or COBOL and is very troublesome to replace. (Not that all VB6 or COBOL code is bad, mind you, but as soon as you get out of their problem domain things go downhill fast.)
Then there's ColdFusion.
--
(In all seriousness, I'm sure there's good ColdFusion code out there, but the stuff I've seen is like a weird mish-mash of all the bad parts of PHP with all the bad parts of ORMs and all the bad parts of XSLT.)
- lostapathy 10y agoThis, exactly. It's like a case study in all the bad things that can go wrong when you mix government projects run by people who didn't know what they were doing with 10-15 years of neglect, but need to keep the software alive because it supports a critical government function but there's nowhere near the budget to rebuild it properly.