Typing. Love it or hate it, it has many advantages: better DX (through intellisense auto-completion),... Tagged with javascript.

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Typescript, hello native typing for Javascript, it has many advantages: better DX (through intellisense auto-completion), better code documentation, less time consuming errors. The State of the Octoverse 2022 shows the impressive popularity ofTypescript in 2022, which means this need to evolve becomes almost mandatory.

Goodbye Typescript, hello native typing for Javascript ✨

What will native JS typing look like if this proposal passes?

<p>Article is misleading. The proposal is not about bringing type checking to JS, it’s about adding/isolating syntatic space for JS supersets like TS and allowing code with said syntax to run without transpilation. Type checking will still have to be done by external tooling (like TS). I believe this proposal is useless. Here’s why:</p>
<ul>
<li>This has nothing to do with actual type checking. Even if it did, TS would win over year long TC39 processes to get stuff added to spec in this domain rendering this proposal useless.</li>
<li>This doesn’t solve transpilation issue. We need the tooling for things like language features or jsx anyway. And we need optimised bundles for production. This just adds additional stuff to be removed.</li>
<li>Let the likes of TS innovate and do their thing. Constraining/steering their syntax to what seems reasonable today is shortsighted. Imagine if this proposal landed years ago with something akin to jsdoc syntax to steer the direction of typed supersets of JS.</li>
</ul>


<p>Very interesting article indeed. I do welcome native typing to JS. I think it would just remove the frustration of another config file to manage, one less dependency on a project, etc. But what intrigues me is, where native typing in JS and TS can co-exist; I assuming this as a positive since TS is fully built out for type-safety and JS native typing won’t have everything from the beginning. Exciting stuff here. Great read!</p>
