Comments on: Name Soup http://infrequently.org/2008/08/the-ecmajavascript-name-soup/ Thu, 09 Feb 2012 21:30:02 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: alex http://infrequently.org/2008/08/the-ecmajavascript-name-soup/comment-page-1/#comment-234989 alex Tue, 19 Aug 2008 17:55:18 +0000 http://alex.dojotoolkit.org/?p=736#comment-234989 hey Daniel: Your first paragraph is spot-on. 3.1 is a very short-term set of improvements and bug fixes to the language while Harmony will be the next version past that. As for Class-based semantics, I think the big problem w/ what was being proposed for ES4 wasn't that classes were being made available, it was that they were being shoe-horned into a language which already had classes but no syntax for them and therefore it was duplicating lots of things to add the semantics you're familiar with. Prototypal inheritance isn't bad, but it's not enough. Class-based inheritance and straight-up multiple inheritance has 20 years of being proven to be terrible for many tasks. We need something in the middle, be they "interfaces with bodies", real semantics for mixins, or Traits. Regards hey Daniel:

Your first paragraph is spot-on. 3.1 is a very short-term set of improvements and bug fixes to the language while Harmony will be the next version past that.

As for Class-based semantics, I think the big problem w/ what was being proposed for ES4 wasn’t that classes were being made available, it was that they were being shoe-horned into a language which already had classes but no syntax for them and therefore it was duplicating lots of things to add the semantics you’re familiar with. Prototypal inheritance isn’t bad, but it’s not enough. Class-based inheritance and straight-up multiple inheritance has 20 years of being proven to be terrible for many tasks. We need something in the middle, be they “interfaces with bodies”, real semantics for mixins, or Traits.

Regards

]]> By: pipwerks.com » Blog Archive » ECMAScript vs JavaScript vs ActionScript: Do you know the difference? http://infrequently.org/2008/08/the-ecmajavascript-name-soup/comment-page-1/#comment-234986 pipwerks.com » Blog Archive » ECMAScript vs JavaScript vs ActionScript: Do you know the difference? Tue, 19 Aug 2008 15:50:50 +0000 http://alex.dojotoolkit.org/?p=736#comment-234986 [...] Russell has provided definitions for many of the ECMAScript-related names you might be reading about these days, including [...] [...] Russell has provided definitions for many of the ECMAScript-related names you might be reading about these days, including [...]

]]> By: Ajaxian » ECMA What? Harmony Who? TC39? Tamarin? JavaScript! http://infrequently.org/2008/08/the-ecmajavascript-name-soup/comment-page-1/#comment-234984 Ajaxian » ECMA What? Harmony Who? TC39? Tamarin? JavaScript! Tue, 19 Aug 2008 12:48:34 +0000 http://alex.dojotoolkit.org/?p=736#comment-234984 [...] Alex Russell has seen the confusion of the many names that were bandied around with the Harmony news last week. There are so many names, that involve specs, projects, and general technical jargon that it can get a little confusing. Alex has made it very clear: [...] [...] Alex Russell has seen the confusion of the many names that were bandied around with the Harmony news last week. There are so many names, that involve specs, projects, and general technical jargon that it can get a little confusing. Alex has made it very clear: [...]

]]> By: daniel http://infrequently.org/2008/08/the-ecmajavascript-name-soup/comment-page-1/#comment-234983 daniel Tue, 19 Aug 2008 09:25:41 +0000 http://alex.dojotoolkit.org/?p=736#comment-234983 I may be dumb but I still don't understand what the nature of the changes that have been agreed to are. If I understand correctly ES3.1 will be implemented in the short term, then Harmony. ES3.1 includes just a set of small changes but the general form of Javascript doesn't change much. Harmony will then introduce changes to the shape of your javascript code with features like class-based semantics ? To be honest I would assume most of the people looking in from the outside like me are mostly interested in when it will become easier for them to code javascript by adopting some familiar class-based semantics. I may be dumb but I still don’t understand what the nature of the changes that have been agreed to are. If I understand correctly ES3.1 will be implemented in the short term, then Harmony. ES3.1 includes just a set of small changes but the general form of Javascript doesn’t change much. Harmony will then introduce changes to the shape of your javascript code with features like class-based semantics ?

To be honest I would assume most of the people looking in from the outside like me are mostly interested in when it will become easier for them to code javascript by adopting some familiar class-based semantics.

]]>