Not making excuses: just sharing observations. Well, there are just situations where their transparency falls down, either when they don’t offer much of any at all (as in this case), or in the recent updates to CF20 (where they had a prerelease, but the updates that came out last week were not those we had been working with in the prerelease).īut then I can report also that there was very little activity/interaction from the community in the prerelease, so perhaps they are again feeling damned if they do, damned if they don’t. Maybe the delay means they WILL come out with something that WILL impress MOST of those who try it. Those who used it before will complain of what it lacks, while those who never used CFB will complain if it “barely does more than existing vscode CFML extensions”.Īdobe seems in kind of a damned-if-they-do-damned-if-they-don’t situation, at least with this first version. Indeed, I won’t be surprised if few are satisfied with the new CF Builder. That said, I suspect that MOST people never used even half the capability of that previous version.

To that point, they did dampen our expectations by saying that we should not expect the first version to have anywhere near all the capability that the previous Eclipse-based edition did. Perhaps they are struggling with what to include in a 1.0 release vs what to hold for 1 1.1 or 1.2. 🙂 Perhaps it’s taking more effort than they originally expected. I don’t think we need “wonder”, but only to “wait”.

Adobe coldfusion 11 demo