How JavaScript Works: deep dive into call, apply, and bind

Re:How JavaScript Works: deep dive into call, apply, and bind by moron4hire on Friday July 09, 2021 @08:20PM (#27789929)

Not recommended if you have lots of objects with this interface. Each object will have its own copy of each function. Using a class with the methods in a prototype ensures there is only one copy for all object instances.

It also makes specialization and calling super methods super verbose.

And you've ultimately not done anything other than reimplementing OOP, poorly.

[ Parent | on HN ]

Re:How JavaScript Works: deep dive into call, apply, and bind by bokwoon on Friday July 09, 2021 @09:52PM (#27790457)

You're not supposed to use `super` or specialization with factory functions, call the functions you need instead.

OOP inheritance does not belong in this pattern, even if you could hamfist it in (which you've already observed as unwieldy).

[ Parent | on HN ]