Since I was name-checked in this thread...
So, when Macromedia bought Allaire, they placed several of the Allaire execs in senior positions and my team of C++ and Java devs were told "you will use CF for all the website stuff" and they put Jer in charge of my team (he was a lot of fun to work for). Jer was also obsessed with Flash, so we created an all-new
macromedia.com in CFML with a fancy expanding overlaid Flash-based navigation system. Similarly, we built an all-new online store with Flash and CF and an all-new Extension/Exchange site and we also replaced the download center with a CFML app.
We selected Mach II as the framework for a lot of that (which caused some accusations of "favoritism" from the Fusebox crowd and some others). When I oversaw the Oracle ERP integration project a while later, I used Model-Glue.
And so, for a while, every single online purchase, every single download, every single license purchase, for all Macromedia products went through CFML (and some Flash).
The Flash navigation was a disaster so that was removed in favor of plain HTML/CSS/JS. The project nearly didn't launch at all because the JRun connector was so incredibly buggy... but after a couple of bugfix-focused updaters to CFMX, we got it all launched.
Over my time there, the Flash gradually all went away in favor of plain HTML/CSS/JS but it was still all backed by CF. For a while, the CF team used
macromedia.com as an acceptance test before releasing new versions -- so we were always running each new CF release
prior to the public getting access.
One thing about Macromedia: every team could pretty much do whatever it wanted, in terms of technology. That meant multiple bug trackers, multiple version control systems, and all sorts of random programming languages across the entire company, along with a mix of third-party systems, all cobbled together with string and tape. One of my early large projects internally was to get a JMQ message hub in place and at least replace all of the batch jobs and ad hoc file transfers with real-time messaging. That's how the JMS gateway for CF came about that shipped as an example.
And then Adobe bought us. Adobe has corporate standards for everything. One of the first battles we waged was JBoss vs WebLogic. Sigh. And they wanted us to standardize on Oracle for the database too. Also sigh. And Perforce was inflicted on everyone for version control. And SAP was the answer to everything, in terms of HR, ERP, CRM, etc. So a huge amount of the integration work my team had done over the previous five or six years was all torn out and thrown away.
And then the CFML-powered parts of the website all began to go away in favor of whatever awful corporate content management systems etc Adobe had deemed were the "standard" for the company. And all the teams' bug trackers were "standardized" too.
And that's why there's next to no CFML used at Adobe any more.