JavaScript was an elegant prototype-based class-free language until TypeScript and ES6 classes ruined it.

Yegor256 Blog offers insights, opinions, and discussions on software development, engineering practices, and technology trends. Covering topics such as object-oriented programming, code simplicity, and software design principles, Yegor256 Blog provides resources for developers and tech enthusiasts. Developers can explore unconventional ideas, challenge conventional wisdom, and broaden their perspectives on software craftsmanship through Yegor's blog posts and essays.

Yegor's Blog

JavaScript was originally designed as an elegant prototype-based, class-free language inspired by Scheme and Self, featuring dynamic typing and first-class functions. The introduction of ES6 classes in 2015 and TypeScript's type annotations fundamentally changed the language's philosophy, importing Java/C++ concepts that conflict with its original object-centric, prototype-based design. These additions cater to developers familiar with class-based languages but undermine JavaScript's unique contribution to programming: class-free object-oriented programming with duck typing and prototypal inheritance.

The Fall of JavaScript

IMO adding classes to JS was a mistake but TS is great

One Day You Come Back To JavaScript Then You Say “The Rise Of JavaScript” Then You Remember Me Rookie!

I believe in Type Script supremacy

We’ve seen the rise of NoSQL document databases, and the concept of schema-on-read versus schema-on-write. So why does anyone have an issue with ducktyping and prototype inheritance? IMHO the similarities are obvious.

Somewhat agree with some of the points. I barely write JavaScript with classes. Maybe if I need a service or something here and there. But I am pretty sure I could create the same thing with regular objects or just functions exported from a module. I don’t necessarily think adding classes killed the language. To me that’s just trying to be a purist. It’s there when you need it. If you don’t need it, you can just stick to POJOs. Besides, classes are just syntactic sugar for regular objects. I guess the point about trying to appease the Java and C++ crowds is true in that regard.
I also love TypeScript. I think it’s a necessary evil. These days I am just not going to start a project without TypeScript. Why guess what things are in my apps when we have spent the last 10+years coming up with IDEs that can help us. Some even say TypeScript is just a glorified VS code extension. It’s a joke of course, but it really helps IDE intellisence which in turn helps me. This is especially true if I have spent quite some time away from a project or when trying to onboard into an exisiting project.