_getify

8 ms·

121.
by _getify 13y ago
I think you'll see in part 3 (should be published tomorrow) why I'm arguing that "objects-only" is the MUCH simpler way to get [[Prototype]] styled code (that is, "behavior delegation"). However, it requires you to stop using constructors a
122.
by _getify 13y ago
I will not be directly addressing "parasitic inheritance" as I never saw it to be a terribly useful pattern, honestly. I see it very rarely used and even more rarely referenced by that name. The point I'd make about it here, though, which i
123.
by _getify 13y ago
In part 2, which should be published today, I'll be addressing "class { }" and why I think it doesn't belong in JS. I think it's just more "distraction" that moves us away from a better clearer understanding of how [[Prototype]] behavior de
124.
by _getify 13y ago
Actually, the evolution of the language has been adding "class-like" features over time. It was most definitely not designed originally to mimic classes. That's been the demand of all the classicists coming to the language. There are those
125.
by _getify 13y ago
In part 2, which should be published later today, I am going to address "polymorphism" directly, and the punchline is that I'm going to argue that JS doesn't have a good "OO" way of doing relative super calls, and thus you should try to avo
126.
by _getify 13y ago
As the OP, I would argue that your metaphor actually does match well how delegation works not only in the real world, but also in JS. For example, if I'm given a task by my boss, and he says "just make sure it gets done", I'll have a set of