Extreme, yes which is why almost no one commented on the idea I guess. But being a long time CF developer (10+ years) the I was extremely glad when openBD and Railo came along. I even consider moving to one of them before they were open source engines. My frustration with ACF and MCF (Macromedia CF) goes way back. But I am not here to air those but to promote CFML going forward.
If the Advisory Committee was started again or something like it that would be a good thing. Andrew Penhorwood Sunday, February 13, 2011, 12:35:59 PM, you wrote: > "Forking and renaming" seems a bit extreme. But, it seems that the > recent changes at Adobe regarding ColdFusion product management > creates an opportunity for OpenBD and Railo to restart the CFML > Advisory Committee--just because Adobe quit doesn't mean the committee > can't or shouldn't continue (maybe it should even be renamed to the > "Open CFML Advisory Committee", and the spec it produces would be the > "Open CFML" spec). > On Feb 11, 6:47 pm, Andrew Penhorwood <[email protected]> wrote: >> >> I can't make it to the openCF Summit. But here is my idea on how to make CF >> great again. >> Fork the language and call it something different. Between Railo and OpenBD >> fix all of the strange ideas added to the language by Macromedia and Adobe. >> Not one wants to program in Pascal but people are writing cool stuff in >> Delphi (which is a flavor of Pascal). They just don't call it Pascal. The >> marketing world is full of ideas like this, repackage it and it sales again. -- Best regards, Andrew Penhorwood [email protected] www.coldbits.com 336-501-0958 cell -- tag/function ref: http://www.openbluedragon.org/manual/ mailing list - http://groups.google.com/group/openbd?hl=en Get to Texas in Feb for OpenCFSummit http://www.opencfsummit.org/
