I Switched from TypeScript to ReScript
medium.com
I Switched from TypeScript to ReScript
1–10 of 49 posts
Re: I Switched from TypeScript to ReScript
#2Cool story bro
Re: I Switched from TypeScript to ReScript
#3Why not simply use Javascript? Today it's a fine language. You may complain about fatigue etc which I can buy, but Rescript is simply not solving that.
Re: I Switched from TypeScript to ReScript
#4I was using TypeScript all through 2019. Went back to plain old JavaScript at the beginning of 2020. Still using plain old JavaScript by default, and break out React when I _really_ have to. No regrets, many benefits.
Re: I Switched from TypeScript to ReScript
#5Why not simply use Javascript? Today it's a fine language. You may complain about fatigue etc which I can buy, but Rescript is simply not solving that.
the only reason I'm using typescript over javascript is types, once I converted a huge code base, there were instances where I fed javascript wrong number of args, or just wrong type of args and it did work (failing subtly on runtime), otherwise is perfectly fine.
Re: I Switched from TypeScript to ReScript
#6> ReScript is not just a rebranding: it’s a ReasonML which freed itself of the yoke of the OCaml ecosystem. By doing so, it forfeited compilation to native code and OCaml library interop, but gained a freer syntax which further resembles JavaScript
See also BuckleScript & Reason are now called ReScript:
Re: I Switched from TypeScript to ReScript
#7> ReScript is not just a rebranding: it’s a ReasonML which freed itself of the yoke of the OCaml ecosystem. By doing so, it forfeited compilation to native code and OCaml library interop, but gained a freer syntax which further resembles JavaScript See also BuckleScript & Reason are now called ReScript : https://rescript-lang.org/bucklescript-rebranding
Here's a great comment explaining all the permutations:
https://news.ycombinator.com/item?id=25426438
At least from a branding perspective, it seems the whole thing has been quite bungled. But obviously what's more relevant is how well the technical goals actually get met.
Re: I Switched from TypeScript to ReScript
#8I was using TypeScript all through 2019. Went back to plain old JavaScript at the beginning of 2020. Still using plain old JavaScript by default, and break out React when I _really_ have to. No regrets, many benefits.
typescript is liteally a superset of js.
what are your benefits
Re: I Switched from TypeScript to ReScript
#9I'm actually a fan of JavaScript. Even though TypeScript/ReScript might add some cool features, I don't feel the urge to switch...
Re: I Switched from TypeScript to ReScript
#10I think the best point in the article is this:
> ReScript, as with other statically typed functional languages, aims at changing the way code is approached at a fundamental level.
We currently have a project written in ReScript and it's an absolute nightmare. Most of our stack is JavaScript/TypeScript/Flow, so no one can just jump in and work on it very easily - they first have to learn ReScript and all of it's different concepts, approaches, and nuances (or refresh themselves if they've done that but haven't worked on the project in a while). It's a HUGE context switch. At least TypeScript is a superset of JavaScript so it's very easy to get up to speed on for a JavaScript developer, and switch between.
For a side project this is fun. But I would never consider this for a "real-world" project (i.e. something you get paid for). At least not anytime soon. Maybe in a few years if there's wider adoption, but that's a long way off.