[UPDATE: The spots filled up. Registration is now closed. Next stops: Munich, Amsterdam, and London...]
i've just learned that registration for the chicago stop on my actionscript 3.0 training tour has been re-opened. apparently some new spots have opened up. the event is on december 3rd, 2007.
hope to see you there!
the Reference Implementation is actually very easy to set up and use. to get started with it, watch John Resig's short video explaining basics of installation, and compiling and running programs.
of course, the Reference Implementation doesn't include the Flash Player API or a Web browser API (e.g., the DOM), so you can't actually create any visuals with your code, but you can try out the new core language features, such as block scope (let), multimethods/method overloading (generic functions), and iterators.
if you have some (well, a lot of) time on your hands, and you're curious to see some not-so-internal debate on the future of ECMAScript 4 between Microsoft, Yahoo!, Adobe, Mozilla, Opera, "and others," start here:
a few quotations from brendan, to give you the flavour of the discussion:
~"I created JS, so I can speak more authentically than whoever was quoted above: I love JS too, quirks and all, but the idea that it should be kept small, like a Toy Poodle, while giant companies such as Microsoft and Yahoo! are purveying and propagating onto the Web proprietary Rottweiler languages -- JS-beating programming languages with ES4-like features -- and even hyping such languages against JS (see the rigged C# chess demo from Mix07 that MS wrote to show up the JScript version of the same program: http://primates.ximian.com/~miguel/pictures/mix-chess.png) -- this is a breathtaking imposture."
~"The insinuation that someone was passing a self-described overview off as a spec is not a "fact", it's a lie from the anonymous miscreant."
~"(I stopped reading /. long ago, as having my own small children to look after involved less chin-wiping and was more edifying and entertaining. :-)"
~"kris zyp wrote:
> I think that if even 25% subset of ES4 was uniformly
> implemented in all browsers in 10 years, web developers
> would be vastly further along than if the 100% of ES4
> was implemented in half the browsers.
You're kidding, right? Ten years is far too long, and there's no coherent 25% -- a lot of ES4 depends on the type system. Would you cut that and try to stitch the remaining pieces back together? King Solomon only offered to bisect a child to find the true mother. Quartering was not a good idea even for that purpose. Anyway, Microsoft is now the avowed anti-mother of ES4, so you are only going to help mutilate or kill ES4 with this kind of bargaining. "
if you have time to wade through the entire discussion, you'll stumble upon many interesting links. have fun...