|
|
|
|
|
|
by toastercat
1104 days ago
|
|
|
> I don't even mind the classes - just because it makes Crockford and the other enterprise java folks shut up This is the second time I've seen in this thread that people lump Crockford in with Java enterprise folks, but Crockford routinely says `class` was the worst addition to JS. > What I do find particularly impressive is how flexible JS is, and how much support can be added without actually changing the runtime Funny enough, this sounds a lot like something Crockford would say. I think Crockford's main gripe with JS these days is that TC39 is more concerned with adding superfluous features than cleaning up footguns. There is a video from 2018 where he goes through some of the more popular ES6 features and mentioned which ones he likes/dislikes. [1] [1] https://www.youtube.com/watch?v=XFTOG895C7c |
|
|
Because Crockford was one of the people advocating for a particular style of initialization of objects that mirrored classes, but was not directly a class before classes existed in JS. (see: https://crockford.com/javascript/inheritance.html)
It is utterly enterprise and classlike in nature though, and not my cup of tea. Mainly - I just wanted enterprise folks to stop trying to re-invent classes in the language, and the class keyword stopped that behavior.
Big net win for the language in my opinion - even though I personally still don't use classes all that often.
---
His modern take is fairly reasonable, though.