Types in JavaScript: why you should care

jcemer.com

26 pointsjcemer5 comments

Since the author advocates for the use of Flow it is implicitly exposing the lack of a typing system in JS, but I wish the community was more explicit and critical about this fundamental problem.

All the new features of ES6/7/8 are great, but in the case of types the TC39 needs to adopt a more radical posture.

Agreed, but how to get it on the agenda?

According to their Github[1]:

> To make a feature request, post to the es-discuss mailing list. Your goal will be to convince others that your proposal is a useful addition to the language and recruit TC39 members to help turn your request into a proposal and shepherd it into the language.

Apparently here: https://esdiscuss.org/

[1] https://github.com/tc39/ecma262/blob/master/CONTRIBUTING.md

I think everyone who wants typing is using TypeScript, which is ES8 with optional typing.

Nobody in the JS community wants to make typing mandatory.

Typing could be perfectly optional like in the ES4 proposal 10 years ago.

Using TS is great for pure JS, but certain libs like Vue are still problematic. A "native" solution would be much better than TS or Flow.

Reply on news.ycombinator.com