3 ms·

Yet another day, yet another incomplete and immature language comparison blog ! I really wish to see some mature blog post which in depth covers the merits of

Yet another day, yet another incomplete and immature language comparison blog ! I really wish to see some mature blog post which in depth covers the merits of languages in comparison by writing a large enough and workable piece of code solving the identical problem and utilizing all features of individual languages in their specific codebase. If the author would have been really unbiased about TypeScript he must have mentioned at least 2 (but not exhaustive) following things. 1. Advance TypeScript Types https://www.typescriptlang.org/docs/handbook/advanced-types.html https://www.typescriptlang.org/docs/handbook/advanced-types.... 2. Number of existing JS libraries TypeScript already supports https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types https://github.com/DefinitelyTyped/DefinitelyTyped/tree/mast... Most people are just stuck with ES5 and callbacks. I have conducted many (about 12 so far) meetups here in India on new features of ES6/ES7/ES8 and using them to build small full-stack JS/TS assignment with TDD for various kind of senior devs coming from Go, Java, Scala, Python and Ruby. Common reaction from them I receive very often "We never knew that JS/TS can do that"

a0 7y ago
> Common reaction from them I receive very often "We never knew that JS/TS can do that" Maybe it's about what you cannot do in ReasonML, and not about what you can do in TypeScript? :)
nirvdrum 7y ago
The author mentions DefinitelyTyped: "DefinitelyTyped typings amount is just insane and it will take time for ReasonML to match them." I agree it would be nice to have an expert analysis of a reasonably-sized application, but that is a rather large undertaking. And frankly many devs aren't experts in two "competing" ecosystems. If you spend the bulk of your time in ReasonML, you're apt to fall behind on TypeScript's recent developments. What you see as bias may just be simple ignorance. I've just started playing around with ReasonML in the past week, and everything the author has hit upon has been relevant. Writing reducers in ReasonML is a treat. But, the language server isn't nearly as good and there aren't many annotated libraries, so I have to fall back to BuckleScript's JS interop support. The interop system is well-done, but it's extra overhead I wouldn't have to deal with otherwise.
- loxs 7y ago
  "it will take time for ReasonML to match them" Nope, it will never match them if they both keep their current speed. The contrary - the rift will become bigger and bigger.
  - nirvdrum 7y ago
    I didn't make the claim nor am I supporting it. But the author definitely mentioned DefinitelyTyped as a positive for TypeScript.
    - loxs 7y ago
      I know. It was not a comment to your words, but to OPs, just to give more info to people not familiar.
      - nirvdrum 7y ago
        Gotcha. My misunderstanding.
yawaramin 7y ago
I wrote something like that: https://dev.to/yawaramin/typing-and-code-flow-in-typescript-and-reasonml-2paj https://dev.to/yawaramin/typing-and-code-flow-in-typescript-... I tried to be as objective as possible, since I am using TypeScript a bit in my day job (main project uses Flow though). Anyway, even when working on the simplest code example for the comparison, I still found more gotchas than I'd have expected.

a0 7y ago

> Common reaction from them I receive very often "We never knew that JS/TS can do that" Maybe it's about what you cannot do in ReasonML, and not about what you can do in TypeScript? :)

nirvdrum 7y ago

The author mentions DefinitelyTyped: "DefinitelyTyped typings amount is just insane and it will take time for ReasonML to match them." I agree it would be nice to have an expert analysis of a reasonably-sized application, but that is a rather large undertaking. And frankly many devs aren't experts in two "competing" ecosystems. If you spend the bulk of your time in ReasonML, you're apt to fall behind on TypeScript's recent developments. What you see as bias may just be simple ignorance. I've just started playing around with ReasonML in the past week, and everything the author has hit upon has been relevant. Writing reducers in ReasonML is a treat. But, the language server isn't nearly as good and there aren't many annotated libraries, so I have to fall back to BuckleScript's JS interop support. The interop system is well-done, but it's extra overhead I wouldn't have to deal with otherwise.

loxs 7y ago
"it will take time for ReasonML to match them" Nope, it will never match them if they both keep their current speed. The contrary - the rift will become bigger and bigger.
- nirvdrum 7y ago
  I didn't make the claim nor am I supporting it. But the author definitely mentioned DefinitelyTyped as a positive for TypeScript.
  - loxs 7y ago
    I know. It was not a comment to your words, but to OPs, just to give more info to people not familiar.
    - nirvdrum 7y ago
      Gotcha. My misunderstanding.

yawaramin 7y ago

I wrote something like that: https://dev.to/yawaramin/typing-and-code-flow-in-typescript-and-reasonml-2paj https://dev.to/yawaramin/typing-and-code-flow-in-typescript-... I tried to be as objective as possible, since I am using TypeScript a bit in my day job (main project uses Flow though). Anyway, even when working on the simplest code example for the comparison, I still found more gotchas than I'd have expected.