Ι quite enjoyed гeading it, yοu cаn be a great author.I will be sure to bookmark your blog and may come bacκ at some point. I want tо enсourage уou to definitelу continue уour great posts, have a nice morning!

http://www.fosteгсlub.com/members/i80equipment

A must read artiсle!

httρ://gumboo.org/2011/11/used-bucket-truck-ѕaleѕ/

http://ωww.serieѕ7eхamprep.com/category/ѕeries-7/

Τalk soоn!

http://tumсseymour.org/page14.ρhp

http://ωww.amazon.com/Hardyѕ-Ваne-Workοut-Dіet-ebook/dр/Β009RХ5TSO

The people who respond in this manner need to channel their anger better. This topic should galvanise the community and dare I say ACF into action. But what sort of action? I don’t know exactly.

I think Mark was onto something when he mentioned the way ACF is marketed - i.e. to management rather than to developers. Management’s engagement with technology is too high level and does not foster the loyalty needed to create a buzz about a technology. Have you seen management at your local User Group meeting? How about a code war, seen management there?

From what I have seen, programmers treat and defend their favourite language with all the zeal of a fanatic and this is a problem because it throttles their desire to learn new languages. I have started looking into python and found Udacity a good resource for learning. However, there will always be die hard {insert language here} fans.

So from ACF’s point of view they need to recognise that developers have a propensity for fanaticism because they spend their working day using tools (language|IDE|plugins|extensions etc) to solve a myriad of problems. This is where that seed of fanaticism is sown - so this is where ACF and the community should focus their energy if they want to see it flourish. Charging more for licenses will give you some profit in the short term, but won’t guarantee the longevity of the product.

This is a tough question to answer. @Billy touched on this when he said “I have a ton of ideas on how we can build that ecosystem, but I can’t help but wonder if that’s the best use of my time.”

I think people need to make this decision on their own - depending on their own work position, what they see themselves doing in the future etc. That being said, as I said on the podcast, I think it’s an economy of scale issue - there just aren’t as many people writing stuff on / for ColdFusion to let them catch up to other languages out there, so I think it will be tough to catch up.

Honestly, I’m personally focusing my energy on other languages at this point and time. However I am part of a team that is maintaining a reasonably large ColdFusion code base, so I expect I’ll still be writing ColdFusion for quite a while longer.

So I think it boils down to a simple question - what are your priorities? Only you can answer that.

One hope I’ve had over the years is that if Adobe ever threw in the towel with CF they would at least open source the code. Actually, I’m certain they would increase CF mind share if they open sourced it now and continued to develop the product. Obviously, they’d have to rethink how they can monetize it.

Maybe I’ll eat my words someday (and I don’t mind if that happens), but I don’t get all the enthusiasm for Railo. I definitely don’t mean any disrespect for those working on Railo; I just feel it’s a niche of a niche.

Eric Pierce

One thing I found myself asking was, is it possible to right the ship? You brought up a lot of things that are either lacking in the ACF product, or strategies that Adobe should be using to reach the widest possible audience. But my question is: Assuming they were to do all of that, and hypothetically do it well, do you think we even _could_ see a resurgence of CF in the web-development ecosystem as a whole? Or is the decline too deeply entrenched now, and all efforts (herculean or otherwise) can only hope to slow the process?

Interested to hear your thoughts.

Thanks for the time spent doing these podcasts.

Hats off to the both of you (and the team) running cfObj(anz) for the last 4 years. (Gutted I missed this one!)

Heard someone say the other day: “if you are not learning something new, you are going backwards” sooooo true for this industry!

Cheers

When I started w/ CF back in 2001, work was slow for me (was new to contracting) and I realized shortly after if I couldn’t get a customer to buy CF…I’d lose work. So I took off and learned multiple languages in the past 10 years. It has benefited GREATLY!

I bashed C#/ASP.NET then came to love it. Loathed Java then found a great respect for it. Rails was a joke and now it is my de facto. Python (learning it now) was meh but I’m starting to see promise in it.

The problem with all of those first thoughts is they were based on preconceived notions based on other developers hating on another language. .NET’ers hate on CF, CF hates on Ruby/Rails, etc, etc, etc. It breeds closed minded developers.

“A closed mind doesn’t get fed.” - Me, regarding idle hands (no work for language X so I am idle)

It was great to hear your reasoning behind the languages you’re choosing to work with beyond CFML. Everyone will have different reasons and we should expect to see a wide range of opinions on this (for all my dislike of JavaScript, I think Node.js will have an important position in the new web world, even if it is only used as a proxy for the browser to access a variety of back end services). I really think the shift to polyglot systems is a given and we’ll see modular, communicating processes - rather than monolithic web apps - as you said. In fact, Chris Richardson (”Plain Old Java Objects” author and founder of Cloud Foundry) gave a talk on just that subject to the local Java user group this week!

@Dale - The issues surrounding Adobe sponsoring cf.Objective(ANZ) started well before my (lack) of application for ACP came into fruition. That whole saga dates back to ~ January of this year. It just solidified my desire to not reapply to be an ACP.

Re: “clearer direction to which both of you guys are moving to ” - I had thought we touched on the languages we are both starting to work with (I mentions JRuby, and I know Kai mentioned doing more JS and Clojure as well).

We also outlined the steps we’d advise for picking a new language to work with that works for you and your team. (We had a whole section on it). Let me know if they didn’t make sense, I’d be happy to clarify further.

However I agree with most of the points of the discussion.

What would have been good is a clearer direction to which both of you guys are moving to and what your favourite language / technology is.

Cheers.

– Adam