31–39 of 39 posts
If PureScript is Haskell, TypeScript is ML Lately, TypeScript has become more scalable across existing npm libraries and also introduced new advanced types. It looks like Microsoft guys learned a lot from C# and F# type system and feedback from their users https://www.typescriptlang.org/docs/handbook/advanced-types....
I had the impression: ClojureScript == Lisp PureScript == Haskell Reason == ML TypeScript == C#
If PureScript is Haskell, TypeScript is ML Lately, TypeScript has become more scalable across existing npm libraries and also introduced new advanced types. It looks like Microsoft guys learned a lot from C# and F# type system and feedback from their users https://www.typescriptlang.org/docs/handbook/advanced-types....
Typescript is Javascript with a relatively advanced type system (mapped types, type guards, etc) on top, but is still very much constrained by Javascript fundamentals and syntax.
The type system evolution was primarily driven by the need to create valid typings for the existing JS ecosystem, and this noticeably shapes the capabilities.
This is the right choice for the language, but I can't see how it resembles the ML family much.
Earlier quoted context omitted.
Don't get me wrong. I love PureScript and HKT but the fact that it requires complete buyout to Purescript ecosystem overwhelms my team members and becomes a hard sell. To build a PS layer on top existing JS libraries isn't straight forward. Now that they introduced so many breaking changes, it will take time for other PS libraries to catch up. May be I might go back to PS when 1.0 release happens and I hope many thin…
It really didn't take long for libraries to catch up, we already released a Package Set compatible with 0.13, two days after the release. That's a set of the most used ~200 libraries in the ecosystem. https://github.com/purescript/package-sets/releases/tag/psc-...
i'd tread very carefully and wisely before choosing any one of these paths.
it only makes sense imo if you come from Haskell, Clojure, or some other ML background to have an explicit interest in these languages.
If PureScript is Haskell, TypeScript is ML Lately, TypeScript has become more scalable across existing npm libraries and also introduced new advanced types. It looks like Microsoft guys learned a lot from C# and F# type system and feedback from their users https://www.typescriptlang.org/docs/handbook/advanced-types....
I had the impression: ClojureScript == Lisp PureScript == Haskell Reason == ML TypeScript == C#
But now Typescript 3.5 is also influenced by F# which is close to ML.
Just look at those advance types and their allowed composition which Typescript supports in its latest release and you will understand.
Earlier quoted context omitted.
I had the impression: ClojureScript == Lisp PureScript == Haskell Reason == ML TypeScript == C#
Yes. I agree. It was started like this. But now Typescript 3.5 is also influenced by F# which is close to ML. Just look at those advance types and their allowed composition which Typescript supports in its latest release and you will understand.
what is scary about all these TypeScript, PureScript, Elm, etc, is that for variety of reasons, any one of these can just come and go. coffeescript anyone? i'd tread very carefully and wisely before choosing any one of these paths. it only makes sense imo if you come from Haskell, Clojure, or some other ML background to have an explicit interest in these languages.
what is scary about all these TypeScript, PureScript, Elm, etc, is that for variety of reasons, any one of these can just come and go. coffeescript anyone? i'd tread very carefully and wisely before choosing any one of these paths. it only makes sense imo if you come from Haskell, Clojure, or some other ML background to have an explicit interest in these languages.
Elm, PureScript, and Clojurescript are fundamentally different languages. Javascript today has bloated, and it keeps growing. Experienced developers tend to dislike it. Newbie developers struggle with it. It is no longer "a small language with a low entry barrier". ECMAScript specification is already bigger than Java's.
PLs of today and the next couple of decades will be striving for optimizing for programmer's productivity, performance, or correctness of the program. Javascript today does not fit in any of these categories. So it is only natural - the trend of using alt-js langs will only grow.