Adobe's actions speak loudly about their lack of support for ColdFusion
ColdFusion
I keep hearing from Adobe that it stands behind ColdFusion today and from here on out, and by all accounts if you based your perception on the continual development of the product you would think that it is definitely a part of their focus. We are already hearing CF9 features for goodness sake!
If this is true, why is it that the Adobe marketing seems so out of step with this message?
When I attended the Flex 3 kickoff meeting for the Dallas Flex User Group, they used an Adobe presentation that went into some detail about talked about server-side language interoperability with Flex, explicitly citing .Net, Java, PHP, yet they apparently didn't feel that their own product ColdFusion made the cut. Given how gracefully the two work together, coupled with the fact that it is their product, how can that really be excused? Actually as I look back at that post, I pondered that question here.
This past week someone posted the following image to our ColdFusion User Group list asking why Adobe would so obviously exclude ColdFusion when showing showing various languages talking to Flex and posted this image from the Adobe site.
***EDIT: Adobe has updated the image below since the time of this blog posting***

I mean... come ON! That seems like such a glaring and purposeful ommission.
Earlier this year, I received the shirt below from Adobe. It irked me when I got it, but after seeing this theme of publicly dismissing ColdFusion over and over, I took a picture of it last night for this post. Here is the "entire" Adobe family as seen through their eyes.

Adobe, I truly want to believe that you support ColdFusion and I repeatedly try to convince my my employers and clients that you are, but over and over, you continually weaken my case.
If this is true, why is it that the Adobe marketing seems so out of step with this message?
When I attended the Flex 3 kickoff meeting for the Dallas Flex User Group, they used an Adobe presentation that went into some detail about talked about server-side language interoperability with Flex, explicitly citing .Net, Java, PHP, yet they apparently didn't feel that their own product ColdFusion made the cut. Given how gracefully the two work together, coupled with the fact that it is their product, how can that really be excused? Actually as I look back at that post, I pondered that question here.
This past week someone posted the following image to our ColdFusion User Group list asking why Adobe would so obviously exclude ColdFusion when showing showing various languages talking to Flex and posted this image from the Adobe site.
***EDIT: Adobe has updated the image below since the time of this blog posting***

I mean... come ON! That seems like such a glaring and purposeful ommission.
Earlier this year, I received the shirt below from Adobe. It irked me when I got it, but after seeing this theme of publicly dismissing ColdFusion over and over, I took a picture of it last night for this post. Here is the "entire" Adobe family as seen through their eyes.

Adobe, I truly want to believe that you support ColdFusion and I repeatedly try to convince my my employers and clients that you are, but over and over, you continually weaken my case.







Loading....