Live data from Hacker News

How to rewrite classes using closures in JavaScript

gaurangtandon.com

11–20 of 58 posts

Re: How to rewrite classes using closures in JavaScript

#12
There are private properties in classes

class Foo { #ImPrivate = true; #meToo() { if(this.#ImPrivate) cantTouchThis(); } }

new Foo().#meToo() === BOOM

Also with using closures for "classes" takes up a whole lot more memory because new instances off all the closures are created for each instance of the class.

Re: How to rewrite classes using closures in JavaScript

#14
I'll never work with someone like the author in a team.

Just because of your personal opinions and certain things that don't matter in the end, you want to ruin everybody's development experience.

The proposed solution is way uglier than the standard syntax, and you'll be lucky to get any intellisense or type checking out of it.

Re: How to rewrite classes using closures in JavaScript

#17
The venerable master Qc Na was walking with his student, Anton. Hoping to prompt the master into a discussion, Anton said "Master, I have heard that objects are a very good thing - is this true?" Qc Na looked pityingly at his student and replied, "Foolish pupil - objects are merely a poor man's closures."

Chastised, Anton took his leave from his master and returned to his cell, intent on studying closures. He carefully read the entire "Lambda: The Ultimate..." series of papers and its cousins, and implemented a small Scheme interpreter with a closure-based object system. He learned much, and looked forward to informing his master of his progress.

On his next walk with Qc Na, Anton attempted to impress his master by saying "Master, I have diligently studied the matter, and now understand that objects are truly a poor man's closures." Qc Na responded by hitting Anton with his stick, saying "When will you learn? Closures are a poor man's object." At that moment, Anton became enlightened.

https://wiki.c2.com/?ClosuresAndObjectsAreEquivalent

Post reply on HN