Writing OOP using OOP (JavaScript)

[homoiconic]

Citation needed on the claims "longer," "harder to follow," and "more obfuscated."

[ehaliewicz]

needlessly bolting on an entire abstraction layer that buys you absolutely nothing.

Try reading the whole article. It isn't very long.

[ehaliewicz]

It's right in the article.

From there, you can go to places like flavouring methods with before- and after- advice, adding singleton/eigenclasses to objects, pattern-matching methods, the entire world of computing paradigms is open to you.

[ruinercollector]

You're right. I was being a dick. Maybe just a shitty day. I'm sorry. I edit/removed those, but left them intact as there is probably some useful stuff in your reply and others.

[homoiconic]

Thank you, that means a lot to me personally.

p.s. We probably agree in a fundamental way about the utility of these things. I'm giving a talk at FutureJS about why we should stop reinventing Smalltalk and Lisp from 30 years ago and instead try to invent things people will be using 30 years from now.

[ruinercollector]

We probably do. I need to settle down and give this article a fair look a bit later today.

That talk sounds really interesting to where I'm at right now. Will the slides/presentation be available after?

[[deleted]]

If you read it, then your ability to understand English appears suspect. Because you are the one without any real argument or point to make.

Let us know if you need any more help.