| node.js is appealing due to unification and sharing of code in front and back end, cf can't offer that |
| Adobe price gauging and staggering contempt for customers. |
| Market Perception |
| Lack of good educational materials/courses |
| we embrace it |
| Bad design choices by both Adobe and Lucee |
| new network dept doesn't want to support it |
| "CooldFusion is dying" is unnecessarily inflammatory. But let's say it's sunsetting / in maintenance mode as a concept. |
| The market (AUTO) hates CF as it doesnt create MAKE WORK, as management uses IT issues a dumping ground for their lack of vision, intelligence and leadership |
| Enterprise direction to unify tech stack to .net c# |
| No free and open code repositories or plugins |
| Small community compared to other languages |
| buggy framework plugins, not enough users to test |
| Due to Adobe not doing anything CF related in Europe, most companies don't even know CF exists |
| the tooling for coldfusion is in a poor state compared with many other offerings. no autocomplete, few debuggers, no static analysis, no bolted on static type system, etc. typos are an expected runtime thing. null handling is terrible. the null coalescing operators ?: and ?. do nothing to resolve the issue, and don't work for bracket access or function calls. |
| Coldfusion updates breaks things from time to time |
| Adobe is useless, hence we moved to Lucee a few years ago. |
| I find that moving CF code to production on the AWS cloud is challenging. |
| The development and bug reporting processes are opaque and difficult to follow. The language is fine. The community has withered. |
| Lacking of modern infrastructure |
| CIO tries to make the claim CF is not secure to use. |
| CF will have an image problem until reputation improves. that can only be done by adobe. |
| Adobe is a poor steward of the language |
| lack of CF SDKs out there for integration with popular tools in e-com/martech/payment, etc. |
| New hires do not know or embrace CF |
