Open adamcameron opened 8 years ago
Shame,
If it's accepting peer contributions perhaps the community will step up with the effort of maintaining the variances, was suggesting internally that this resource would form part of our training docs so happy to help keep the Lucee element current ?
On Friday, 15 January 2016, Adam notifications@github.com wrote:
IE: remove references to Lucee, align CFML to ColdFusion's dialect, change comparative references to ColdFusion to just be CFML.
Except chapter 0, obviously
— Reply to this email directly or view it on GitHub https://github.com/adamcameron/cfml24h/issues/28.
Alex Skinner Managing Director
Pixl8 Interactive, 3 Tun Yard, Peardon Street, London SW8 3HT, United Kingdom
T: +44 [0] 845 260 0726• W: www.pixl8.co.uk• E: info@pixl8.co.uk
Follow us on: Facebook http://www.facebook.com/pixl8 Twitter http://www.twitter.com/pixl8 LinkedIn http://www.linkedin.com/pixl8
CONFIDENTIAL AND PRIVILEGED - This e-mail and any attachment is intended solely for the addressee, is strictly confidential and may also be subject to legal, professional or other privilege or may be protected by work product immunity or other legal rules. If you are not the addressee please do not read, print, re-transmit, store or act in reliance on it or any attachments. Instead, please email it back to the sender and then immediately permanently delete it. Pixl8 Interactive Ltd Registered in England. Registered number: 04336501. Registered office: 8 Spur Road, Cosham, Portsmouth, Hampshire, PO6 3EB
Well in Lucee's own theory, anything that works for ColdFusion's CFML should work on Lucee's CFML too already.
TBH, it was trying to write this doc in a vendor-neutral way - and whata a ball-ache it was becoming dealing with Lucee's divergences - that pretty much put me off Lucee completely. It was just a mistake for Railo then Lucee to go their own way with CFML, for the purposes of "CFML solidarity".
It also makes CFML look a bit amateurish to have to explain the differences. Most of Lucee's divergences are just "nuisance" ones, IMO, and really don't add to CFML when seen in the broader context.
As far as peer contribution goes, 90% of what a Lucee-only user would write would still apply equally to ColdFusion's CFML, would it not? I don't see it as a barrier to contribution.
I do not intend for this to be "against" Lucee, I just don't want to busy myself with all the differences, as it's really not relevant to most CFML users. It's just clutter.
That said, I'm happy to add an appendix which covers Lucee divergences? It would def be helpful, and might cover your requirements too?
IE: remove references to Lucee, align CFML to ColdFusion's dialect, change comparative references to ColdFusion to just be CFML.
Except chapter 0, obviously