TeraTech

The ColdFusion Experts: Develop, Secure, Optimize

067 More you missed from Adobe ColdFusion 10, 11, And 2016 with Charlie Arehart

By Michaela Light Leave a Comment

Charlie Arehart talks about “More you missed from Adobe ColdFusion 10, 11, And 2016” in this episode of the CF Alive Podcast, with host Michaela Light.

Are you moving up to CF2016, or maybe 11? In doing so, are you skipping over 11, or perhaps even 10, in that move?

Shops often drag their feet upgrading from one version of CF to another and may well skip multiple releases in the process, so that they may not have paid attention to what was new in the release(s) skipped. Can you name the top 5 or 10 features/changes in these three most recent releases?

In this presentation, veteran CFer Charlie Arehart will help fill these gaps for you, highlighting the top features of 10, 11, and 2016, along with some hidden gems. (Whereas his classic “hidden gems” talks have gone deep to uncover a few dozen features per release, this talk will necessarily focus on just some key ones.) With demos and resources for learning more, you'll be in a better position to take full advantage of your new CF installation.

Episode highlights

  • What are the top features CFers may have missed
  • Isn’t CF10 end of life?
    • Yes but lots of people still running it (or CF9) ← security risk!
    • State of CF Union Survey
  • With CF 2018 about to come out why should CFers care about these “old” features?
  • JVM changes – in CF 10 and forward
    • JRUN → Tomcat
  • Cloud deployment shifts
  • The Elvis operator
  • 100% cfscript is possible as of CF 11
  • No day zero security issues for 4+ years
  • CF Summit East
  • CF conferences in DC
    • Allaire DevCon 2000
    • CFUnited-08
    • 20th anniversary of first CF conf in FT Collins CO Robi Sen
      • CFUN in NIH

Mentioned in this episode

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

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.

ColdFusion Alive by Michaela Light 067 More you missed from Adobe ColdFusion 10, 11, And 2016 with Charlie Arehart
00:00:00 00:00:00
Facebook Twitter Google Embed

Bio

A veteran server troubleshooter who’s worked in enterprise IT for more than three decades, Charlie Arehart (@carehart) is a longtime community contributor who as an independent consultant provides short-term, remote, on-demand troubleshooting/tuning assistance for organizations of all sizes and experience levels (carehart.org/consulting).

 

Interview transcript

Michaela:         Welcome back to the show. And today, we're gonna be looking at what you may have missed in C.F. 10, 11, and 2016 with Charlie Arehart. And if you don't know Charlie which I find hard to believe because everyone knows Charlie in the C.F. world. He is a veteran ColdFusion trouble shooter. He's been doing it since like the first version came out and he's been an I.T. wizard for like more than three decades now I think. But right now, he helps out people with their ColdFusion servers.

So when they're sick or not doing what they should be doing. And what we’ll look at today is something you may not have considered. There may be bunch of features in older versions of ColdFusion that are still in the version of ColdFusion used today that you don't even know about. So we’ll talk about that. And we'll also talk about C.F. Summit East where Charlie will be speaking. And if we had a chance, we'll reminisce about some of the other conferences in Washington D.C. So welcome Charlie.

Charlie:            Hey there! Thanks for doing this as always. It's great that you do that for the community.

Michaela:         You’re so welcome. So isn't ColdFusion 10 gone end of life? Why would anyone care what features were in C.F. 10?

Charlie:            Sure, sure, so you know and that's reasonable question. The point of the presentation is that as I've been helping people over the past several years ten years, 20 years now. And I'm sure you can attest to this yourself that people don't migrate up as quickly as the new releases come out. So there are people that today are still running on C.F. 9 or, and here's the bigger point. They say, “Well I'm on nine anymore. I've moved up to 11 or 2016.” Well often they will have skipped let's say ten. And so ten was such a watershed release compared to nine or earlier ten and later are quite different because nine on earlier ran on JRun and ten and later on Tomcat. So I just use that as a marking point to say for anybody that maybe jumped from nine or earlier to ten or later, these are things to be aware of.

Read more

Related Posts