Most of the new features of CF are customer suggestions/requests. TheThe wishlist is not public; it is just a form on their site that could be directed to /dev/null for all we know. Previews and conference sessions don't really draw the kind of input I am referring to. They may show a new feature like PDF generation and get a sense for how it would be received or again get input on additional features. But there is no opportunity to really deal with more fundamental changes like CFCs.
wishlist is public and there were many pre-beta previews, focus groups and
other opportunities for input. I remember sessions at DevCon three years
ago for Neo.
I do wish that the process was more formalized. I'd prefer to see CFMLI don't think it is a good idea to open source CFML. However, the language specification should be opened up and some sort of formal process should be put in place for changes to it. We now have more than one CFML vendor and that means there can be cost savings for the vendors and the customers if a single language specification was agreed on. I know that when I talk with the New Atlanta folks they reveal all sorts of interesting undocumented behavior in CF. Apparently, they used to trust the documentation until code in the wild proved that wasn't a safe bet. While that may seem like their problem, it is actually our problem. What happens if one of us was relying on some behavior that was intended and as such is later changed. That means we have to change our code if we upgrade, which means it costs us more money to upgrade or we don't upgrade at all, which costs the vendor money.
open-sourced or at least have a formal, open specification but lacking that
I think there's a lot that can be done to borrow from those processes even
for a closed-source system.
BTW, in testing BD 6.1b2 it seems that using cfinclude in CFCs works as expected and thus not compatible with CFMX. How's that for irony?
-Matt
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
