43. What aspects of CF are keeping you and/or your company using it? (Check all that apply)*
|The CF systems/devs have a history of delivering projects on time. Previous attempts to replace us have led to shitty, un-extendable and expensive software|
|Good language/platform. Switching is expensive and there's little motivation to do so.|
|old apps written in cf, would not use it for new apps|
|More flexible than other languages (aka duck typing and alike)|
|Faster, more flexible than other middleware.|
|Fast to code|
|Only developer, only language I know.|
|You should rewrite this question to "What aspects of CF keep you and/or your company using it?|
|Everything is already CFML and no reason to move away.|
|Easier to support many custom applications long term due to fewer library dependancies.|
|One of the top reasons is CommandBox. CFML has lost the edge in most areas, unfortunately.|
|We are migrating from CF|
|Fast to code in|
|Richness offered by ACF (PDF Generation, Spreadsheets, web sockets, etc)|
|from using what?|
|it is what we like|
44. What aspects of CF are preventing you or your company from embracing CF? (Check all that apply)*
|corporate IT wants all office365|
|we don't have any issues with CF|
|The community size is small, so there's a lot more that you need to do yourself and your more likely to encounter bugs.|
|Lack of widespread support for a Framework|
|Missing great linting and inline debuggers.|
|Unfounded reputation that it's outdated.|
|Java or C#...that's enterprise. 🙁|
|Management Thinking ColdFusion as obsolete tech|
|Cultural issues. CF has a stigma.|
|Insufficient staff to tackle more and/or larger projects; supervisor does not want department to assume responsibility for larger, more time-consuming projects|
|More people should get behind lucee|
|outsiders bashing CF|
|Lack of resources to hire developers|
|community small, so bugs are not discovered very fast|
|Lack of customisation/extensibility for Adobe CF|
|This is begging the question.|
|You forgot 'none' as an option.|
|Small community and online resourced|
45. What are your company’s plans for your technology stack, if any? (Check all that apply)*
If migrating FROM CFML to another language, please specify
|managers want to evaluate what our stack will be going forward|
|Java, python, nodejs|
|our application is composite it will move to node,java or go depending on requirements|
|Java or .Net|
|Node ( NextJS )|
|A lot of CFML is being rewritten as microservices in Go - which I think is a mistake.|
|node.js // python|
|Porting existing CFML apps over to PowerApps.|
|Node.js for backend tasks|
|Ruby or Python|
|Moving functionality to consolidate overlaps|
|.net and Java|
|frontend development in VueJS|
If migrating from another language TO CFML, please specify
|Java or .Net|
|Ruby on Rails|
46. What is your approximate salary range in USD? (Remember, this is anonymous) (Check one)
|Not from us|
|There is no other. I am retired so I code for free to small businesses that couldn't afford a database driven web application.|
47. What is your current arrangement for CF work? (Check all that apply)*
|Self Employed (owner of company, not sole trader)|
48. What percentage of your PROFESSIONAL development time is spent on CFML (as opposed to other languages)? (Check one)*
49. What percentage of your HOBBY development time is spent on CFML (as opposed to other languages)? (Check one)*
50. Any additional comments/suggestions for the survey?
It would be interesting to have a question about which devs/blogs people read or follow on Twitter etc...
We would never - under any circumstances - pay for a web programming language/platform. If not for Lucee, CFML would have been in the rear view mirror ages ago.
Thanks for doing this! I look forward to seeing the results.
I really love CF and worked with it for many years ...
I think the licensing model of CF is killing this language. the kind of thinking (8 cores for one enterprise-license) is out of todays needs and reality - even hard to find a server with 8 cores only :-))) i switched to VMs and there the costs of the license it is even more strange to me. it should be at least countable for 32 VM-cores or more ...
young developers will choose other languages and technologies.
stop using AWS products as categories, use 'serverless' for instance as each cloud has it's own name and AWS is a dogs breakfast atm which is why we're never intending to use them again.
Nothing about using message queues and other tech here. Nothing about ML either.
Also no talk of technology stacks really around cf, what WAF other than cf-based ones, etc
There's a few sets radio/checkbox answers here that could benefit from "dunno" / "N/A"
REST in Peace!
I love ColdFusion but it is being destroyed.
Please put ColdFusion back in the USA with better marketing and sales and better communicators and better support and better training. Hire professionals. Hire back in the USA for better coders and better coding. Testing. Test this stuff please.
Get out and explain that this is a JVM or Java fronting language.
1. I don't understand why you are not doing a scientific survey. It would be much more accurate.
2. I don't use any frameworks because I don't know how to use them. Training classes would be helpful.
3. It would be good to conduct qualitative research after you get the results from this survey. I would recommend a focus group on a particular survey question.
Adobe killed CF. Lucee is a great retirement home for legacy CFML apps to live out the remainder of their lives, but it will never know the glory days of old again.
I love CFML. I've championed it at every employer I've worked for in the past 20+ years. I wrote and maintain trycf.com. I'd love to see it catch up to the modern stack, but that will not happen. ACF is too slow to introduce language features because fluff features pay the bills. (API manager, CFClient, etc...). They are also too slow to upkeep their fluff (hibernate, extjs, etc...). Likewise, Lucee is too afraid to move away from ACF compatibility and therefore are stuck in the same decade's old mindset. It sucks, but that's the way it is.
Far too long have we pretended that CFML is easy. I work with a lot of OO CFML that is by far the most complicated (unnecessarily) and hard to debug code I've ever seen. That's not all (much of it, but not all) CFML's fault, but OO is hard, with very little benefit. Too much mysterious mutations happening and no telling where functions, data, variables come from or why they change. ColdBox, sorry, but it sucks by association. It tries to help the not really-OO-language-but-tries-to-look-like-it, but it falls short (don't tell the Ortus folks, they're awesome and do an awesome job, but ColdBox is too OO for not enough gain -- too much black box!). FW/1 is much simpler, but not as many resources (human, oss, support, etc...). Functional programming is also hard, but has so many benefits that overcome all the headache we've found in OO programming. It is impossible to achieve anything close to pure FP in CFML (not that pure would be good either), which is one major reason we're ditching it. Moving to a much flatter more manageable and readable code platform that is much leaner and can spin up and be deployed much faster (nodeJS servers & serverless AWS Lambda).
CommandBox and especially the ComamndBox docker image and CFConfig are awesome and are far ahead of many web tech stacks out there, but developers like to use modern language features that make their jobs easier and their code better. CFML just doesn't see that, never have, never will.
I'll likely continue the CFML ride until the end, but as a manager and one responsible for hiring and tech decisions, I will not be doing any new development in CFML.
We are migrating away from CF. Both in my last company we migrated from CF. It is hard to justify cost in open source world. It is very very difficult to get good CF developers who has experience in OOPS. It is definitely not easy to find CF jobs to advance the career. There is not single job in California in my salary range.
Share these results with Mark Takata at Adobe! And anyone else that has responsibility for promoting and improving CF.
Community is good and helpful, like most developer communities. It's also small (compared to communities for languages/environments with much wider adoption) and the Adobe team is unhelpful in most cases, especially with support for ACF performance and ColdFusion API Manager.
Thanks for putting these together each year. 🙂
Adobe has to fix the licensing per core issue. Last time we ordered new servers I had to custom order Dell to get 4 core CPUs so I could get by with a mere 2x Standard Licenses per server. Most standard CPUs in servers are 8-16 cores. No one is going to pay $5,000 for a server + Windows and then $25,000 for CF. You want to force people to Lucee? THIS is how you force people to Lucee.
Love CFML. My personal stuff is all done in Lucee.
Where you had operating systems you did not have Unix we use Oracle Solaris
Question about conference should have been altered due to the pandemic nobody can move at the moment.
Total number of responses
8. Wrap up (Final Page)
Join the CF Alive revolutionDiscover how we can all make CF more alive, modern and secure this year. Join other ColdFusion developers and managers in the CF Alive Inner Circle today.
- Get early access to the CF Alive book and videos
- Be part of a new movement for improving CF's perception in the world.
- Contribute to the CF Alive revolution
- Connect with other CF developers and managers
- There is no cost to membership.