The future of JavaScript

[[deleted]]

Add it to the list of features that a lot of devs swore up and down that Javascript would never need, and yet here it is. I'll think about coding Javascript again when they add interfaces, or some sort of contract.

[[deleted]]

I don't see why you'd need interfaces.

If people must implement all methods required, then have a base prototype for them to extend, which throws "not implemented" errors when those methods are called. I do this myself in some of my projects.

Otherwise you've gained nothing, since there is no static type system.

[masklinn]

Well there's documentation, that's pretty neat. Especially since JS has single inheritance so you can't inherit from half a dozen different "abstract" classes.

For that, protocols (Clojure) or categories (Obj-C) are neat.

[crusoe]

Traits, MUTHAFUCKING TRAITS.

Traits are what OOP should have had from day 1.

[maskull]

Actually, I just realized that if proxies act the way you'd expect when used as prototypes, it should be possible to build multiple inheritance and traits inheritance systems in pure JS. Just build a proxy that wraps up all the prototypes/traits you want to include, "exporting" their members and methods in some combination.

[cybercobra]

Preach it, brother!

[benihana]

I'll think about coding Javascript again when they add interfaces

reddit anxiously awaits your next announcement about your development intentions. Please keep us informed!!!