3 ms·

It's a cute idea, but <cfquery> or bust! I wrote ColdFusion professionally for 7 years in the mid-'00s and I quite liked it back then. The issue, of course, wa

It's a cute idea, but <cfquery> or bust! I wrote ColdFusion professionally for 7 years in the mid-'00s and I quite liked it back then. The issue, of course, was code organization and sprawl because you couldn't easily detach the logic from the view. Still, <cfquery> blocks and <cfloop>s around the results were one of the fastest ways to get something up on a page and working, in the days before very mature frameworks existed yet. It also forced everyone to know everything, so you could point to any dev on the team and they mostly understood the HTML, the CSS, the JS on the page, and the backend. I think the industry trend toward specialization is useful in some cases, but it has made organizations and products almost intolerably complex in many cases where it isn't strictly necessary for the product itself.

bdcravens 4y ago
We still have some production code that I support, but for the most part I've moved on from CF. Still, it is the language that established my career, in many ways. Custom tags well before client-side components were the rage, in-memory SQL engine (ie, take any recordset and query against it using SQL, without hitting a database), etc are features I still wish for using things like Ruby and server-side JS. The community and to a lesser degree Adobe tried to address the advantages other platforms had (like a first-class package manager) but it was too little, too late. Still, tools like CommandBox and the rest of the tooling by Ortus are actually pretty great. I do find it interesting that client-side frameworks are "rediscovering" patterns from 25+ years ago :-)