2 ms·
I view the draw away from OO as a feature and not a bug. Classical OO patterns should have never been introduced into JavaScript, and it had a just fine object
by tyri_kai_psomi 7y ago
I view the draw away from OO as a feature and not a bug. Classical OO patterns should have never been introduced into JavaScript, and it had a just fine object model, that no one ever took the time to understand properly, for those small use cases it was called for. Emphasizing the functional aspects of JavaScript, it's clear strength, is the right call.
It just seemed like it was thrown in there because Java and C# developers who were increasingly being forced to use JavaScript begrudgingly just couldn't live without their "class" keywords, so they took to the forums to make JavaScript more like a "real" language.
- shantly 7y ago> it had a just fine object model, that no one ever took the time to understand properly Plenty of the people who dislike Javascript's prototypal inheritance model and (relatedly) scoping rules do understand them.
- deleted 7y ago[deleted]