Karma, I can concur with your observation that there are no seeming plans for Adobe to drop CF (indeed, they have offered a form on the CF portal to signup for the CF2020 prerelease, when it comes out).
But as for CF support within DW, that seems a christmas wish of yours that will never be fulfilled. There are no signs at all of CF support ever being returned to DW.
I realize you are putting this wish out there for Adobe to consider, and we could leave it at that. But for the sake of some readers, I will add some more perspective to this thread, which your three 2019 comments have resurrected from its originally posting in 2013 and other comments mostly from 2014.
Sure, the situation regarding CF and DW stinks, for those who were/are fans of both. And sure, it is a bad look. But again it's been that way for several years now. It was a decision by the DW team, many of whom wouldn't even know how to spell CF and don't know it exists (and don't care). Should someone at higher levels somehow reconcile the two teams? Sure, but again it's not news that they have not, nor a surprise to most observers that they will not. That trains seems to have left the station long ago, never to return.
So as for CFBuilder, well, the CF Team has begin in the last year to acknowledge how it doesn't work for everyone--but that doesn't mean they think it doesn't work for anyone. The issue is that there are different audiences, who want different things in an editor/IDE. Indeed, you say that DW is "superior" to CFB, but that's simply your stance as a representative of the crowd who want what DW has which CFB does not. There is just as large an audience who never liked DW, and either gravitated to still other non-CFML editors, or tried to make things work with CFEclipse (which like CFB is based on the Eclipse editor). Or there were those who used CF Studio/HomeSite/HomeSite+, some of whom to this day fight tooth and nail to keep those running, even after their support stopped some 15 years ago.
But Adobe's acknowledgement that CFB doesn't work for everyone doesn't mean they will drop it, nor again has there been any news of getting CFML support back into DW (which would seem a call by the DW team). Instead, there have been hints of a possible effort toward implementing an official CF plugin for Visual Studio Code, a free multi-platform editor (vastly different than the old Visual Studio) that has become a darling in not just many CF circles but the larger IT world. But it, too, does not offer the HTML-oriented and web design-centric approach that DW offers.
Sadly, it seems there will never be any single editor that "ticks all the boxes"--which of course would border on impossible, and the same goes for the hope that any move by Adobe regarding editors for CF would please all. So I get it, you've made your plea.
And I don't speak for Adobe. But I offer the above for you, and for any readers who may find this forum thread in the future, offering some perspective from someone watching things from the sideline (I have no strong preference for an editor and work with most all of them, since I support so many folks).
/Charlie (troubleshooter, carehart.org)
35
Replies
AdChoices