ECMA compliance sounds like a good idea.
I'd be interested to hear a commercial business argument in favor of getting Macromedia to spend lots of time and effort on bringing CFSCRIPT up to ECMAScript compliance as opposed to spending that time and effort on adding new functionality to ColdFusion. That's a serious question...
Certainly from a teaching perspective CFML is easier to teach than CFSCRIPT. Well written CFML is very easy to read; more so than CFSCRIPT and generally easier to debug (with regard to the responses from the CF engine).
For existing programmer types it may be annoying to remember to do GTE rather than >= but really?? Is CF going to gain instant respect by virtue of an ECMA facade? I doubt it -- besides its the non-scripting, tag based nature that makes CF so approachable.
It's interesting to see both ASP.NET and JSP moving rapidly toward more XML-like, tag based metaphors in a bid to make them more intuitive.
Personally I'm not sure I understand all the belly-aching going on about CFML. I'd be putting ECMA compliance for CFSCRIPT low on the list of priorities -- it's desirable but not at any significant resourcing cost. Perhaps increase the number of tags available as functions in CFSCRIPT as a compromise.
-- geoff http://www.daemon.com.au/
--- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
