At a prior job (fairly recently, past ~5 years), we still used ColdFusion MX7 for some internal apps and reports. They had been around for a long time, so don't break what works I suppose. :)
The biggest issue with them was that _some_ feature (cfform IIRC) was generating flash .swf input forms, which broke after the flash player EOL. Switching it directly to the plain html version wasn't compatible, so we had to manually fix a bunch of code.
I saw an important app that still used it in a partner organization back when I worked in the federal government. I doubt I can talk to much about the app itself but was actually impressed at how well it held up. Goes to show that legacy applications/tech stacks can hold up just fine if they are thoughtfully maintained.
This page shows some sites still using ColdFusion:
https://w3techs.com/technologies/details/pl-coldfusion
NPS.gov
walgreens.com
acm.org
Cornell University: https://www.cornell.edu/academics/colleges.cfm
FDA: https://www.accessdata.fda.gov/scripts/cber/ReleaseNotes.cfm...
At a prior job (fairly recently, past ~5 years), we still used ColdFusion MX7 for some internal apps and reports. They had been around for a long time, so don't break what works I suppose. :)
The biggest issue with them was that _some_ feature (cfform IIRC) was generating flash .swf input forms, which broke after the flash player EOL. Switching it directly to the plain html version wasn't compatible, so we had to manually fix a bunch of code.
I saw an important app that still used it in a partner organization back when I worked in the federal government. I doubt I can talk to much about the app itself but was actually impressed at how well it held up. Goes to show that legacy applications/tech stacks can hold up just fine if they are thoughtfully maintained.