Adobe CC Deprecated Me!

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.

7 comments

    • Rick Smith says:

      Thanks, but from what I’m reading in the forums that seems to be a workaround that’s hit and miss for users. I’m really not interested in a workaround so much as I need to be using the right tool to do my work correctly.

  1. Since you are getting a bit of a beating in the comments on your CFSummit post, I just wanted to comment here and congratulate for being man enough to say “my problems with ColdFusion being deprecated from Dreamweaver CC were me” and I hope you don’t find CFB as frustrating as some people seem to have done in the past.

    Personally, I loved CFB. I bought 1.0 within minutes of it being launched on the store and upgraded to 2.0 within days of its launch. I found 1.0 good enough to be worth the money and 2.0 is night and day by comparison – so much better. I’m sure 3.0 will be even better still when it ships.

    Don’t forget you can always use CFB in “Express” mode for free once the trial expires (but frankly I found the additional functionality well worth the money).

    That said, I switched away from CFB about two years ago because I wanted one IDE across all my machines and Eclipse + CFEclipse was both too big and slow on my Linux NetBook as well as being a poor shadow of CFB 2.0 (commercial version). With the impending demise of Fireworks (Macromedia moved it into maintenance mode even before Adobe bought them), I switched to a non-Adobe tool (Pixelmator) and never looked back. I hadn’t upgraded Creative Suite since CS4 so when I switched from CFB to Emacs two years ago, I also switched from DW to Emacs. As Apple’s built-in Preview app developed more functionality, I stopped using Acrobat as well, and then some time last year, I uninstalled all Adobe software from all my machines (I haven’t used ColdFusion at all since I switched to Railo four and a half years ago).

    So I strongly sympathize with your criticisms of Adobe but I definitely agree with switching away from DW for CFML development – what little support it had prior to CC was horribly outdated and a very weak feature set compared to CFB.

  2. Maxwell Donathan says:

    I’m just starting with CC and realized that my CF development was made much less productive. A solution that I will be living with is using Adobe Code CC and adding a very nice extension for CF built on the Brackets framework.

    Here’s the list of extensions (almost all) usable in Code CC:
    https://brackets-registry.aboutweb.com/

    Check it out and see what you think. There are a lot of other great extensions from the community that can be used in Adobe Code.

    Best,
    -Max

    • Rick Smith says:

      Thanks Max… I’m certainly paying close attention to extending Brackets as my next CF IDE, but I’m holding out until I fully give Thunder a good hard look too (will post a review on Thunder in the future). My main attraction to Brackets is the frequency of the updates. There’s obviously a very bright future for CF development tools, although I remain extremely frustrated with the abandonment of CF development in DW. I’ve tried Aptana, CF_Eclipse and even just notepad amongst a myriad of others, but I’m now using CFB2 daily. It is PAINFUL at how much longer CF development takes… basic things that were automated are now manual adding days (yes, days) to basic projects. Regardless of the which IDE I use in the end, I can’t wait to return to my former productivity and efficiency with Dreamweaver.

  3. Dawesi says:

    Brackets is already way ahead of ColdFusion builder.

    I think Adobe still have their head up their A** on this one.. at the end of the day a few VP’s and their precious opinions are the reason they aren’t filthy rich, and are just ‘paid well’. Their loss.

    After all the got it right betting the company on flash, oh wait. #adobefailagain

Leave a Reply

Your email address will not be published. Required fields are marked *