To Adobe,
I know you probably can't answer this but what are Adobe's plans for ColdFusion? I get mixed messages, particularly from sister products and your main www.adobe.com web site. Cases in point:
Dreamweaver dropped support for CF when it went CC. I still use CS5 because frankly CFBuilder sucks. DW states "Build the best sites for any browser or device. See how you can quickly create responsive sites, preview them on actual mobile devices, and even extract assets and styles from Adobe Photoshop comps directly into your projects." I also read somewhere where it claimed to be the #1 tool for developing websites but it has better support for PHP and .Net than CF. Is this a veiled statement of the future of CF or simply the DW team not playing well with the CF team?
These forums used to use a CF based forum application, now it's Jive which uses a JSP framework (which again sucks. but I regress). If Adobe does not use CF for their own customer facing portals, what does that say for CF?
Today I received a response for a CF bug I submitted months back, which is fine. When I went to click on the included link, the bug tracker site appears down or half functioning. I could make out a login link, click it and simply received a site error. In retrying while typing this post, now I receive a "no issue found" message. Login still does not work. This does not give a good impression but it leads to my next issue...
Upon going to www.adobe.com to search for the bug tracker location, I found the Feature Request/Bug Report Form. The only field on the first page is a product selection drop-down. If you try to select ColdFusion you'll be very disappointed as ColdFusion does not exist. Is this a veiled statement of the future of CF or simply the product and/or support teams not playing well with the CF team?
Session idea for your CF Summit (which I'm already preregistered), a sit down with various executives and product members (not just from the CF team) on their thoughts of the future for CF (and possibly why they don't get along). It's ok to hear CF team members say how great CF is and all the new and upcoming features, but I think thoughts for other upper Adobe non-CF executives would go a long way to calm the "Adobe hates CF" rumors and impressions.
Idea that I think would re-energize the CF faithful, dump CFBuilder and roll the functionality into Dreamweaver, either natively or as an add-on.