<story><title>From TypeScript to ReScript</title><url>https://www.greyblake.com/blog/from-typescript-to-rescript/</url></story><parent_chain></parent_chain><comment><author>dsnr</author><text>&amp;gt; TypeScript&amp;#x27;s type system is over-complex since it tries to be a superset of JS.&lt;p&gt;This is exactly why it got so popular, and TypeScript support in the JS ecosystem is so good. It&amp;#x27;s easy to just strip the TS metadata and you&amp;#x27;re left with working JS. This is why projects like esbuild managed to ship TS support so quickly (without type-checking).
Good luck doing that with a new language.&lt;p&gt;I for one am &amp;quot;all in&amp;quot; on TypeScript, with all its shortcomings it&amp;#x27;s just the best of both worlds, and so easy to get on board.</text></comment>
<story><title>From TypeScript to ReScript</title><url>https://www.greyblake.com/blog/from-typescript-to-rescript/</url></story><parent_chain></parent_chain><comment><author>jatins</author><text>In my experience with these typed alternatives to JS, as long as you stay within that language things are good and smooth. But as soon as you need to interface with 3rd part lib, that&amp;#x27;s when things start to get messy.&lt;p&gt;Providing type declarations for every third party lib you might want to use, especially in an ecosystem like Javascript&amp;#x27;s which relies heavily on them, gets tiring pretty fast.&lt;p&gt;Typescript manages to get past that because it has reached a level of adoption now that most popular libraries will have a @types&amp;#x2F;&amp;lt;lib&amp;gt; package also but it took a long while to reach that stage.&lt;p&gt;Curious if anyone has used ReScript at a larger scale (and does not have the resources of, say, Facebook) and what&amp;#x27;s their experience been like.</text></comment>