4 ms·
In mid-2000s Microsoft (of all orgs) was actually very opposed to the idea of bringing C++/Java-like classes into Javascript because they have quite an impedanc
by dmitriid 5y ago
In mid-2000s Microsoft (of all orgs) was actually very opposed to the idea of bringing C++/Java-like classes into Javascript because they have quite an impedance mismatch with prototype-based nature of JS.
I'd say, they were right.
- iSnow 5y agoAnd then MS invented Typescript and it was all classes onward... I don't really get it either, and I am saying this as someone who codes in both JS and Java. While thinking in OOP concepts comes naturally for me, I found the prototype/function based approach of JS a breeze of fresh air. I guess the turning point was when JS migrated to the backend and more complex business logic was written in JS. As long as you are basically rendering view state or filtering data, traditional JS is much easier. But write the business logic of some enterprise app, and you want to use the OOP paradigms.