Today Adobe released ColdFusion Builder 1.0. It's been a long time coming and a lot of people have been patiently waiting for this day. Unfortunately Adobe should have waited longer and fixed more of the outstanding bugs and painful performance issues. Then to add to the insult, the price was set at $299 but that does include Flash Builder 4 Standard. However, I still find it way too high of a price for a product that does NOT measure up. As others will note Flash Builder 4 Standard cost $249 so essentially you are paying $50 for ColdFusion Builder. This is great if you wanted to buy Flash Builder. Many of us never touch Flash so this is not much of a bargain.
Then there are performance issues. ColdFusion Builder is painfully slow when it comes to rebuilding project workspaces. It works fine for little projects, but serious enterprise level web applications with thousands of files and folders, such as what I work on, ColdFusion Builder is just slow or worse yet if just fails and throws errors. I've recorded this as a bug and nothing has been done about the problem as far as I can tell.
Using SVN integration makes ColdFusion Builder even slower. The first letter in IDE stands for "Integrated", so naturally I want my SVN integrated as well and since ColdFusion Builder is based on Eclipse this is easy to do. You have a few choices for Subversion clients. I've tried Subclipse and Subversive. Both are equally slow when added to ColdFusion Builder. Interestingly though both are faster when installed in CFEclipse. The issue in my mind is not the SVN client but ColdFusion Builder itself. Again I logged a bug and it is still not resolved.
ColdFusion Builder is a resource hog. Proof is that during testing the solution to any Out of Memory errors was to simply modify the cfbuilder.ini file (which has the JVM settings) and increase the allocated memory. As it stands now the default memory allocation is 512Mb. That is a big footprint.
There are many other bugs including just basic editing problems like the editor pane shifts to the left when editing long lines that made you have to scroll to the right. Every keystroke the editor shifts left and stays there until you type another character then it shifts right so you can see what you typed and when you type another it shifts left. This has also been logged as a bug by many people and confirmed by Adobe but not fixed.
There are color coding issues and a large number of missing features that you will find in CFStudio, Dreamweaver and CFEclipse. Adobe felt they had to release the product short on features just to have a product released and then upgrade it later.
Upgrading brings me to my final point. The Eclipse foundation allows for updates right in Eclipse. Its a built in feature and you're done after a simple restart. This works great on minor version updates and even some larger point version upgrades. Eventually you do get to a point in the update process where you may be better off doing a full reinstall for example when Eclipse has a major version upgrade. However, ColdFusion Builder does not utilize the update feature. We've never been able to upgrade, during testing, to the next version. Each time it is a full uninstall and then reinstall and set up a NEW workspace. So far I've never been able to reuse an existing workspace. This means with every minor upgrade I've had to reinstall ColdFusion Builder, my Subversive plugin, setup my SVN client and connections, re-import my projects, and redo my ColdFusion settings. I've done this so many times that I started a document just to keep track of the steps I take and to document the fastest and most correct way to install/reinstall ColdFusion Builder. Upon the release of ColdFusion Builder I was hoping to publish that as a blog post so people new to the Eclipse platform could have a quick start guide. Instead I have to recommend that you be very careful in deciding to install ColdFusion Builder unless you are already indoctrinated into the Eclipse way of doing things.
If you are interested in seeing the bugs that are still outstanding or the feature requests for features that have been left out you can view the public bug tracker for ColdFusion Builder at http://cfbugs.adobe.com/bugreport/flexbugui/cfbugtracker/main.html.
I really hope that Adobe addresses the outstanding bugs real soon and releases regular patches via an update site because the last thing I wanted to post this morning was a downer post about ColdFusion Builder. In my humble opinion it is just not ready for the prime time.






#1 by Jake Munson on 3/22/10 - 1:45 PM
#2 by Adam Lehman (Adobe) on 3/22/10 - 2:34 PM
@Jake: Sorry you feel that way, but your stereotype of Adobe couldn't be farther from the truth.
#3 by Wil Genovese on 3/22/10 - 2:59 PM
Bugs:
Bug# 82359 is a big one CFBuilder opens files from wrong location.
Bug# 82358, 82290
Bug#'s 82190,81586,79025,74920
Bug# 82103
Bug# 82419 - no 64bit support on the Mac or on 64Bit Windows.
Adam, the only plugin I use with ColdFusion Builder is Subversive. I use the exact plugin with my CFEclipse installation and I do not experience the same issues. I really do not believe the performance issues can be pawned off on the Eclipse foundation or third party plugins. Well, then again to be fair I am using the 64 Bit version of Eclipse for my CFEclipse install on my Mac. Maybe that is the performance difference. If it is see bug number 82419.
Like I said Adam, the last thing I wanted to do this morning was post a disparaging post about
ColdFusion Builder. I was really hoping these issues would get resolved before it was released.
Wil
#4 by Adam Lehman (Adobe) on 3/22/10 - 3:38 PM
In all fairness, I think you are being a bit unfair and unrealistic here.
Bugs (82359, 82358 & 82290) were filed after ColdFusion Builder was finalized (less than 3 weeks ago) and are already targeted for a fix. We will work to solve these, possibly in a auto-updater, but if they weren't reported after 18+ months of testing (including a massive public betas), are they really the show stoppers you are making them out to be?
Bugs (82190, 81586 & 79025) are marked with the lowest possible severity, just above 'cosmetic'. The definition of this severity is "Low - Easy workaround and only affects a small group".
Bug 82103 was created by the ColdFusion Engineering team. "Syntax checker should throw more meaningful error message for duplicate argument names, instead of saying 'Invalid token at line...'." and marked as a medium severity and is targeted for a fix.
#74920 is an enhancement request, not a bug. It says that the cursor skips 'too many' characters when pressing Crtl + Right Arrow.
As far as the enhancement request for 64-bit support, ColdFusion Builder (like Flash Builder 4) fully supports Win/OSX on 64-bit, but on 32-bit Eclipse. We have some shared libraries used across both products the prevented us from adding 64-bit support in this release. However, I must point out that 64-bit support is important because it removes the 1.4Gb RAM cap imposed by 32-bit. You've already complain about CB using 512MB of RAM...
I really don't mean to come across as defensive, but I think you're blog post really misrepresents the current state of ColdFusion Builder. As you can see, we take every bug and enhancement request very seriously, but they comes a point where you have to ship software and move on to the next version.
-Adam
#5 by John on 3/22/10 - 4:41 PM
#6 by Ben on 3/23/10 - 4:02 AM
#7 by Raymond Camden on 3/23/10 - 4:26 AM
I'm not saying that bug isn't annoying - but it seems like you guys are making a whole lot more out of it then it really is. (imho!)
#8 by Craig McDonald on 3/23/10 - 10:18 PM
It is the single most annoying thing that makes CF Builder frustrating to use daily. I was really hoping this would be fixed before release and am genuine shocked it hasn't been. An editor that can't maintain its position in the editing window is pretty poor IMHO and a bit of a usability showstopper.
I'm sorry to say I simply won't be buying CFBuilder until this particular bug is fixed. I put up with it since it *was* beta software, but for charged, released software, it's unacceptable.
Sorry, but if the Adobe engineers think it's merely cosmetic, I wonder whether they use CFBuilder daily to code?