Agreed. all of these can live side by side. There is no reason for new
<Object> to compete declarative classe s.
I merely caused confusion using the phrase "prototypes as classes" instead
of new <Object>.
as a side note whislt you mentioned .{ and |> I would like to have
programmatic, non declaritive alternatives for those as well. This might
warrant another thread.
On Oct 11, 2011 11:12 PM, "Allen Wirfs-Brock" <[email protected]> wrote:
On Oct 11, 2011, at 1:46 PM, Jake Verbaten wrote: > Yes the prototypes are
still there. But that m...
I agree that new <object> would be a useful feature for ES developers who
want to create prototypal inheritance based abstractions. And along with
super support in ES.next it really enables true self-style programming.
However, I think that talking about such abstractions as "classes" creates
confusions and a unwarranted sense of competition with class declarations.
t isn't an either/or situations* *where we have to choose between primitive
compositional operators or declarative syntax for the most common class
abstraction patterns.
ES objects, new <object>, new <function>, object literals, <|, and .{ would
provide a core set of primitives that can be used support of metaprogramming
implementations of a wide spectrum of object abstraction and composition
models. This is a good think and arguably an important aspect of using ES as
the foundation language of the web platform.
Allen
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
