Comments on: ActionScript 3 and ECMAScript 4

By: nwebb » Flash vs HTML5 - and a few points for HTML5 advocates to consider :)

Wed, 07 Oct 2009 11:29:56 +0000

[...] (known as ECMAScript 3.1) and I guess Adobe couldn’t just hang around. You can read about that here. In Flex 4 there is also a declarative graphics language called FXG. Why didn’t Adobe use [...]

By: Tech tabloids, Project Harmony, and the proposal for a ‘Flash’ tag in HTML5 | Commented Out

Wed, 17 Jun 2009 23:06:55 +0000

[...] The result was quite the opposite, as Adobe was now the odd man out, though some said that it didn’t affect Flash at [...]

By: Prospects - Cheap Ebooks, Tools » Blog Archive » ECMAScript Harmony: New Life for JavaScript

Fri, 13 Mar 2009 08:50:24 +0000

[...] at Ajaxian, and the reactions from other JavaScript notables like John Resig, Douglas Crockford, Mike Chambers, and Alex Russell make worthwhile reading (with varying levels of technical detail). Also, Episode [...]

By: Julianne

Julianne — Sun, 01 Mar 2009 22:00:25 +0000

wasn’t there a new release for this?

By: Keep an Open Eye Eye, Sir » JavaScript 2/ECMAScript 4 Delayed

Keep an Open Eye Eye, Sir » JavaScript 2/ECMAScript 4 Delayed — Sun, 04 Jan 2009 21:50:55 +0000

[...] and Web 2.o in general – so it is very notable that work on ECMAScript 4 has been partitioned or delayed depending on who you consult. Clearly there is a functional and learning burden making the shift to [...]

By: Sundunny » M$ can suck it, or I want my ECMA-4

Sundunny » M$ can suck it, or I want my ECMA-4 — Fri, 14 Nov 2008 01:05:24 +0000

[...] Grant Skinner Mike Chambers Hank Williams Written by sundev in: Uncategorized [...]

By: Riality.de | ES4 is dead, long live Actionscript

Riality.de | ES4 is dead, long live Actionscript — Wed, 12 Nov 2008 17:47:03 +0000

[...] AS3 Orphaned – Microsoft to Blame? | Ru Roh! Adobe Screwed By EcmaScript Standards Agreement |ActionScript 3 and ECMAScript 4 | Thoughts on Harmony | Harmony [...]

By: ES4 est-il mort ? Les dessous de table en images. | tweenpix

ES4 est-il mort ? Les dessous de table en images. | tweenpix — Fri, 17 Oct 2008 09:55:30 +0000

[...] conclusion du billet de Mike Chambers va dans ce sens d’ailleurs, et se veut bien plus rassurante encore: [...]

By: tomsamson

tomsamson — Thu, 28 Aug 2008 12:47:56 +0000

The whole not getting the Ecmascript 4 spec accepted as standard thing is very interesting.
Look at Adobe and all Adobe friendly bloggers. What´s the general view there?
Things in the vein of these things get said and repeated often:
Big evil MS blocked getting it accepted as standard. The parties blocking this are only doing so to block innovation on the web!!! Standards are important. But yes, we will continue to innovate!!!

Come, on, gimme a break!
Let´s have a quick look at the history there: AS1;Flash 6: Flash´s scripting language had evolved till there, had become considerably closer to javascript, many people in the “serious” programming world working in java or C++ laughed, didn´t take flash´s AS serious as programming language, but with time they had to accept that the possibility to combine code and media with ease and flexibility like in few to no other environments allowed to rapidly create nice results not possible in java or C++ in a comparable timeframe.
Flash continued its success story.

Fast forward to today: Adobe obviously wanted to attract way more of the “serious” programmers and get AS respected as serious language, many changes were made then. Thanks to AS3 and the way the newer player/interpreter,GC etc work combining non code generated media with codeside has turned into way more work and has become more time intensive . Thanks to the changes in language flash´s AS is becoming more and more a Java wannabe clone.

So again, Innovation?!? Where´s the innovation in turning AS into a Java clone?!?

The reality is Adobe wants to turn Ecmascript/AS more and more into a Java clone and well, while some more used to Java like workflow like it, many many others obviously don´t like that.
First it was more and more people from the flash community moaning, now The Ecmascript 4 suggested spec was declined by a big group of decission makers.

Its understandable Adobe tries to sell their loss in the most positive way possible but yeah, saying “we want to innovate, the others block that” type things while you reduce more and more what made flash innovative and at the same time copy more and more of another language and forced workflow?
Laughable.

By: Jim Michaels

Jim Michaels — Tue, 26 Aug 2008 07:18:31 +0000

I don’t think this sounds the death knell for ECMAScript 4. Just think of it as a long pause. Much ado about nothing.

As for whether or not to have real classes, I think they are a great addition. practically every language out there has them now in some form or other. it’s JavaScript’s time to step up to the plate. If you want to program in an old style, that’s your business, I’m sure it will let you.

I think it is unfortunate that ECMA halted work on ECMAScript 4 and probably E4X too, the new XML part of JavaScript. I have about 1MB of states+cities+towns+etc XML data I would like converted into structures.

The only think I don’t like about version 4 was that somebody thought it was cute to put python into it. scrap the python additions.