I appreciate some of the things TS has pushed forward in ES, but classes are IMO a concession to devs who couldn't handle not having them, and never should have made it into the spec (sugar or otherwise).
My biggest beefs with TS are:
Trying to treat JS like it's C#
Creating a false sense of security with static types and classes
Obsessing over type checking, when it already exists (just dynamically and documented as easily as writing JSDoc params)
And possibly worse than the false sense of security:
Adding far more to the learning curve for junior devs, when I need them to focus on learning the actual language
The difference is that Rust is strictly typed by default, not a layer on top trying to hack the underlying language into behaving like a statically typed one.
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I appreciate some of the things TS has pushed forward in ES, but classes are IMO a concession to devs who couldn't handle not having them, and never should have made it into the spec (sugar or otherwise).
My biggest beefs with TS are:
And possibly worse than the false sense of security:
Basically add in every point (Node.js and Deno creator) Ryan Dahl made recently in explaining why Deno moved away from TS internally.
I've been warning about all of these points regarding TS for years, even while using it and appreciating some of its features when doing so.
Deno moved away from TS... But moving to Rust. An even more strict statically typed language.
The difference is that Rust is strictly typed by default, not a layer on top trying to hack the underlying language into behaving like a statically typed one.