Good to hear that Adobe is not giving up on a product that has a large legacy following, however the question still remains: Why remove it from Dreamweaver? Why take something away from your customers that use more than one of your products together? To force us to purchase CFBuilder, which does not have the UI tools needed, or version control support?
Perhaps the Adobe team thinks that only programmers write Coldfusion and UI developers write html/css? Those of use that do it all prefer to stay in one program for the entire workflow. I have been loyal to Adobe a couple decades, but my loyalty only goes as far as your willingness to enable a productive workflow. Continued hinderance of the workflow we have built around your products has our entire organization looking for alternatives, and by the sounds of it, many others as well. With being said, is the cost of Not putting CF support into DW worth the community impact? And if you are trying to force us over to CFBuilder..... add it to the creative cloud we all ready pay for.
If the Dreamweaver team is focused on catering to the future of programming and removes CF support what message does that send? And if this is the case I would expect to see much more support for the .js frameworks that are making strides on all top server-side languages.