I used (and occasionally still use) cf eclipse, and have always been very happy with it. However, I honestly don’t agree that Adobe is in the wrong here to put out a whitepaper. They spent a considerable amount of time and money building a new IDE (cmon, Dreamweaver and Homesite+ had their day for CF devs, and even cf eclipse was created to fill the void). CF Builder really provides functionality that is drawing new users to CF. Adobe honestly couldn’t stay out of the market due to the fact that an OSS project existed. They saw the need, filled the need, and IIRC, conferred with certain members of the cf eclipse team. A standalone version was necessary to cater to a specific demographic in the community, as well as hooks to new cf9 features.
As ColdFusion continues to progress over the next few iterations, the IDE will be able to stay in lockstep since Adobe can perform parallel development to keep them in sync.While Adam’s post does read a little negative against cf eclipse, I think the point that should be made is that there are a few options out there, make sure you understand what they are, and that cfB is not a clone of cfE as is the common misconception.
All that being said, I am sure the community will continue to support cf eclipse, and I personally thank each and every member of the cf eclipse team for their dedication.
As an aside, I didn’t hear anything in your article that speaks to the future of cf eclipse, or the direction the project is moving. Perhaps you could bolster support by publishing your product roadmap (forgive me if it exists and I just haven’t seen it) so we could weigh options and the community could contribute if there was reason to do so.I've ways seen cf eclipse as an awesome IDE, but with all open source projects supporting a commercial project, they always seem to be chasing their tail. Personally, I have no issue paying Adobe to ensure my ColdFusion IDE is up to date with the language, as well as is assured continuing development and improvement. I'd like to add that the cf eclipse team has done a great job of supporting the CF community over the last few years, and I suspect they will continue.
So was Adobe wrong to put out the whitepaper comparing features? I'd like to hear what you have to say.