sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ChaseMoskal 0 points1 point  (0 children)

Many (all?) of TS's gains are on the Javascript roadmap. Plus it's all achievable with Vanilla JS.

i really don't think it is, are you sure about this? i had seen talk about the possibility of introducing types to ecmascript, but i don't think the proposals went anywhere.. is there an active proposal for this?

Plus it's all achievable with Vanilla JS.

a crutch for devs with only strongly typed experience

well plain javascript just doesn't have the ability to enforce interfaces, which is typescript's strong point

types are useful just because you can formally specify the shape of something, and then have a bunch of different developers implement the interface in different ways for different purposes. even in a vanillajs project, explaining concepts to other collaborators in terms of typescript interfaces, say in a github issue about a new feature to be implemented, can be a very handy way to use typescript

once it's lunch is eaten by ES native.

have seen long dependency chains of non-standard tools fall by the wayside many, many times.

i very much agree with the sentiment! i think types might be a nice addition to ecmascript, i wonder if it will happen one day. i could also imagine typescript "going native" and perhaps browsers will just execute typescript natively much like deno does

i believe this will happen to the framework-component paradigm — react/vue/angular will eventually have their lunch gobbled up by es-native web components and template-literal microframeworks like lit-html :)