Hello and welcome.

 

In the 2017 State of the CF Union survey report, we have detailed breakdowns of tools and techniques used by the top CFML developers around the world. This time we had 472 responses to the survey, which is slightly lower than last year.

Before we begin with the results, we’d like to thank everyone who participated and responded to this year’s survey. And a special thanks to Brad Wood who helped me edit the survey questions and reviewed the results with me.

If by any chance you are new to ColdFusion, it is a development platform for creating modern web applications on the JVM. The CFML language has tags that resemble HTML syntax for templating HTML and script that resembles JavaScript syntax for writing business logic. It is designed to be powerful, expressive and easy to get started coding in. Many features are built into ColdFusion that require add ons for other languages.

Brad pointed out that it's not just CFML developers and enthusiasts  that read through all of the survey results, and that even Adobe pays attention to the survey as well, so it's good to know that the comments and the results on here are definitely being seen by even the largest players in the CF space.

Everyone's welcome to read the results. They're at the TeraTech survey page and you can all see all the results in as much detail as you care to. Let's just have a look at this.

Table of Contents

1.      What version of CFML Engine do you use?

2.      What type of CFML Engine are you running?

3.      CF Server OS

4.      What OS do you run on your laptop/PC?

5.      What browsers/client platforms do you support in your apps?

6.      Databases

7.      Code frameworks

8.      CF-based CMS

9.      JavaScript libraries

10.  What CSS frameworks do you use?

11.  What CFC dependency injection frameworks and tools do you use?

12.  Persistence frameworks

13.  What testing and mocking frameworks do you use?

14.  What CF features do you use for code reuse?

15.  What do you use for source code control?

16.  What tools/IDEs do you use ?

17.  Browser Dev Tools

18.  How many years have you used CFML?

19.  How many years have you used OO?

20.  Other languages/environments you use

21.  How many CF developers at your organization?

22.  How many total employees at your organization?

23.  ColdFusion user group meetings

24.  Which conferences will/did you attend this year?

What version of CFML Engine do you use?

 

The most popular engine is still CF 11, which was true last year.

It's nice to see the ColdFusion 9 members finally shrinking. It was a version that a lot of people got stuck at for many years, so we feel better about dropping support for that in the ColdBox framework, ColdBox 5, for instance, coming up. CF 11 is still very much on top. 2016 is growing, but it's even behind CF 10 at this point, which is very interesting to see.

Also, there's some interesting numbers here too- Lucee 5 is actually more popular among the survey takers than CF 10 or CF 2016.

It's important to note that this is only out of the people that take the survey, so I do think the people more active in the community that are likely to see the survey are more likely to be using Lucee, but it is very heartening to see a very solid uptake, especially even just in Lucee 5. Of course, now that it's been a year or so you can see the Railo shrinking into oblivion since it's essentially unsupported at this point.

It's interesting to note as well, thinking about these graphs, which versions are still supported.

• Railo at this point has no support.
•  Lucee 4 has support only for security fixes, but it's not seeing enhancements, that's all going to Lucee 5.
• Adobe stack, CF 9 was still a decent chunk of users, that's already outside of the support window, and
• CF 10 is coming right behind.

And, it seems that CF 9 went end of life, about two years ago.

CF 10 I think is maybe just a very short period of time away, so very soon there's going to be quite a chunk of Adobe people that are outside of the support window, which is a little scary to think about. That means not just the support, but also no more security hot fixes is like driving a car with no brakes and praying that nothing comes on the road that you need to stop for.

What type of CFML Engine are you running?

 

There's not much to say about Enterprise versus Standards, quite a lot of people using Enterprise. They are pretty neck and neck. The assumption is that the non-applicables are probably mostly the Lucee user base, since there's no differentiation there. The reason is that you get all the features in the one version. It's either free in one version or free in the other versions.  They probably decided to just go with one.

Interesting note is that back in the early Railo days, there actually used to be a premium version of Railo that had additional features, but that's no longer the case with Lucee.

CF Server OS

 

We can see that most people are using Windows but there's a big chunk of people using Linux or something similar. There's still some Unix flavors out there.

The large Windows use is something that's sort of unique to the ColdFusion and .NET environments probably. If you were to do a similar poll looking at PHP or some of the other popular languages, you'd see an inverse of a lot more Linux users. What's interesting though is there is a solid chunk of Mac people, and this is for the server OS. This means people are hosting their servers on Macs, and that's actually a decent chunk.

Sometimes ColdFusion doesn't work exactly the same on Mac, but maybe they're running a staging server or development server, and they develop on Mac and they're hosting it on a Mac.

 

Follow this link to read the full State of The CF Union 2017 Analysis part 1.

 

Here is the State of The CF Union 2017 Analysis part 2

---

 

And to continue learning how to make your ColdFusion apps more modern and alive, I encourage you to download our free ColdFusion Alive Best Practices Checklist.

Because… perhaps you are responsible for a mission-critical or revenue-generating CF application that you don’t trust 100%, where implementing new features is a painful ad-hoc process with slow turnaround even for simple requests.

What if you have no contingency plan for a sudden developer departure or a server outage? Perhaps every time a new freelancer works on your site, something breaks. Or your application availability, security, and reliability are poor.

And if you are depending on ColdFusion for your job, then you can’t afford to let your CF development methods die on the vine.

You’re making a high-stakes bet that everything is going to be OK using the same old app creation ways in that one language — forever.

All it would take is for your fellow CF developer to quit or for your CIO to decide to leave the (falsely) perceived sinking ship of CFML and you could lose everything—your project, your hard-won CF skills, and possibly even your job.

Luckily, there are a number of simple, logical steps you can take now to protect yourself from these obvious risks.

No Brainer ColdFusion Best Practices to Ensure You Thrive No Matter What Happens Next

ColdFusion Alive Best Practices Checklist

Modern ColdFusion development best practices that reduce stress, inefficiency, project lifecycle costs while simultaneously increasing project velocity and innovation.

√ Easily create a consistent server architecture across development, testing, and production

√ A modern test environment to prevent bugs from spreading

√ Automated continuous integration tools that work well with CF

√ A portable development environment baked into your codebase… for free!

 

Learn about these and many more strategies in our free ColdFusion Alive Best Practices Checklist.