Not really, not much one can learn from ColdFusion. The problem with CF is that it tries to do everything. CF server is a huge monolith, some functionality you'

Not really, not much one can learn from ColdFusion. The problem with CF is that it tries to do everything. CF server is a huge monolith, some functionality you'd never use still loads and occupies the memory. I call it "a bag of memory leaks wrapped in legacy dependencies". Haven’t used it for a few years but back in the day “tuning the JVM" seemed to be a common pattern among the CF folks. Basically, instead of accepting the fact that CF is memory hungry, sometimes not releasing memory correctly and literally consuming gigs of RAM within minutes, everybody tried to find some magical JVM settings that would prevent this behavior. Server used to require rather often restarts. the other thing is, some of libraries used by the CF server, even the most recent versions are years old. It’s not really a problem if you plan on using CFML layer only but if you want to do some more advanced stuff with event gateways, you may find yourself in trouble. For example, I was recently writing some Kafka stuff that supposed to be working as an event gateway. The amount of shading required to deploy the JAR is insane. There are some really nice things though, for example <cfprint> tag would be the sole reason I'd put a CF instance up. Haven't seen anything out there that would handle printers so easily. Personal recommendation would be: if you do not have to, stay away. Nothing new to learn there. I am saying this as a certified Adobe ColdFusion 7 and 8 developer who’s not working with this technology for at least 6 years now. Some people in this thread mention that it’s a benefit that people who know nothing about programming are able to write some working code. I find this a problem often contributing to the issues mentioned above.