So I spent the past day excitedly uninstalling all my CS6 software and “upgrading” to the new Adobe CC. I didn’t want to believe Adobe would no longer develop Fireworks (which I find completely stupid and insane, but whatever), so I figured I’d spend the next 6-12 months teaching myself Illustrator… no biggie. If Rogie can do it, I can do it.
Well not only is Fireworks dead, but lo and behold ColdFusion development has been completely removed from Dreamweaver! What!?! When was this announced? What do I do? I have work due by the end of the week… and I CAN’T REINSTALL CS6!!! Seriously, I physically cannot get my work done!
Putting it politely, Adobe’s not winning me over with CC. It’s overpriced, and with the elimination of Dreamweaver and Fireworks from my toolbox I had immediately written this post as my own ultimate demise, cancelling my CC subscriptions and moving to Corel, Zend & PHP. But as I did research and came up with conclusions as to what I need to do to continue development immediately and in the future (I do have a strong belief in ColdFusion for rapid web development), it’s pretty clear I wasn’t being deprecated so much as I was being forced to evolve. In retrospect, I will not be cancelling my CC subscriptions.
I’m a strong supporter in using the right tool for the right job, which is why I’m so disappointed with Adobe’s choice to bid Fireworks farewell. Fireworks is the right tool for the job. Although I have ample time to adjust to Illustrator since Adobe’s going to continue FW CS6 support, Fireworks remains a much more well suited tool for rapid prototyping for the web. No, I won’t be switching to the slapped in web support of non-vector Photoshop (the way Photoshop handles layers is ridiculously stupid), which is still good for, you guessed it, PHOTOS! Yes, Adobe’s on my crap list.
I don’t have any problems with PHP, I like the language. However I continue to find ColdFusion far more efficient and timely in accomplishing the goals of my clientele. Switching to PHP is not the answer [for me].
So as much as I prefer Dreamweaver to code ColdFusion, Adobe has made it clear their tool for ColdFusion development is CFB. Despite my frustrations with CFB, it’s time I use the right tool for the right job, as this is clearly where Adobe’s going to put it’s time, efforts and finances for the future of CF development. Contrary to the backlash coming about on the Adobe forums, I do not see CF support being removed from Dreamweaver as further alienation of developers, but a push to use the right tool for the right job. CFB is that tool for ColdFusion folks. Clearly, my problems with ColdFusion being deprecated from Dreamweaver CC were me (boy, that’s hard to say… sheesh). On the other hand… now that I can no longer code ColdFusion with Dreamweaver, and I’m shelling out a small fortune each month for multiple licenses, I strongly believe CFB should be included with CC. I’m paying for CC to do web development… Adobe has taken that away from me in Dreamweaver and currently doesn’t allow me to develop for their own software (ColdFusion) in CC. This is a legitimate problem that needs to be fixed. And as much as I dislike CFB, I can only hope (and hopefully contribute if they’ll listen) that CFB3 will be an improvement, which is undoubtedly on the horizon with CF11.