7 ms·
I think they describe well that Typescript needs a lot of complexity by supporting all of JS. That's both a strength and a weakness, easy to get started for peo
by codeptualize 4y ago
I think they describe well that Typescript needs a lot of complexity by supporting all of JS. That's both a strength and a weakness, easy to get started for people who know JS, but typings can get crazy complex.
Rescript has a different approach which has lots of benefits, it is much better in terms of type inference, it's much faster, and I think it's fair to say safer. The tradeoff is that it's not JS, making it harder to adopt.
I do think they are doing a great job in taking steps to present the ocaml origins in more JS friendly patterns and syntax, but it still requires learning some new concepts.
I think a somewhat good comparison is; If Typescript is like C# for JS, Rescript is like F#/ocaml for JS. Different technologies have different tradeoffs.