10 thoughts

  1. Ben,
    This is the beginning of the end for ColdFusion.
    Who will adopt it if Abode’s own IDE’s stop supporting it?
    I have worked with CF since Allaire days and despise CF Builder. If Dreamweaver doesn’t issue a patch for supporting CF fully, then watch CF die as a viable platform accepted by the major compaines in the world.
    Unbelievable that Adobe would do this, do they want CF to die?

  2. I hear you. Except, I’d counter and say that Dreamweaver has never been a true ColdFusion IDE. Even back in Allaire days when I worked with the Macromedia Dreawmeaver team to add ColdFusion support, the support was minimal at best. There was one release (MX maybe?) that added some decent CFC support, but honestly, there has been no real DW support for CF since then, just more of the same. Which is why the ColdFusion team build ColdFusion Builder, and that’s where they are putting their efforts. I understand that you don’t like CF Builder, I’m not a major Eclipse fan myself, but CF Builder is a far better CFML IDE than DW ever was, and so that’s the focus going forward. And yes, use DW myself extensively, so I’ll now need to rebalance the tools I use and when I use them.
    — Ben

  3. Ben,
    But this doesn’t make sense. You can’t even open a cfm page in the new Dreamweaver to see any part of it?? I can open all kinds of other pages and languages in DW, why would they actually exclude cfm from being opened?

  4. And I am hearing from ASP users who are complaining that they can’t open .asp files and have lost ASP server behaviours. So, just to be very clear, it’s not a CF thing. I’ve asked the DW team for clarification and will share what I find out.
    — Ben

  5. So, a little more info …
    ColdFusion support was indeed removed, along with ASP/ASP.NET and JSP. (PHP was left there for now). Going forward Dreamweaver is focused on delivering visual tooling support for relevant front-end web technologies. Some server-side and backend features have been removed (along with some older workflows and legacy clunky UI elements, and more).
    The team has said that in Dreamweaver CC server behaviours will be made available as extensions, and they have promised extensions to address missing functionality (and said that they would be addressing this more broadly within the next week).
    — Ben

  6. Peter, I would only support adding CF Builder to CC is ColdFusion itself were offered as a CC Service. I’d not support CF Builder within CF itself.
    — Ben

  7. "Peter, I would only support adding CF Builder to CC is ColdFusion itself were offered as a CC Service."
    I see where you’re coming from with this, and in theory I’d agree. However, this should be seen as a way to reduce the feeling of being tricked (valid or not) among a number of CF developers. Everyone will have made a calculation of whether they think a CC subscription is worth it for them when they decided to sign up, and for a number of CF developers (probably a considerably higher number than Adobe would like to think), a CF-capable version of DW went into that calculation.
    I’m a hobby photographer and do some part time CF at work and on personal projects, and so the number of apps I really need in the full suite is not that many, so DW certainly amounted to a considerable % of that calculation, and now it won’t even let me edit the html in those files? Adobe can’t possibly have not seen this creating a lot of unnecessarily bad feelings among their customers.
    Also, now that DW CC is apparently just a design tool (unless you use a non-Adobe serverside language such as PHP for some strange reason), where’s the map that explains how all the Edge stuff (Reflow, etc) fits in relation to DW?

Leave a Reply