reason - ReasonML vs TypeScript -
what tradeoffs between reasonml (https://reasonml.github.io/) , typescript (https://www.typescriptlang.org/)?
there many trade-offs, many of them stemming reasonml technically being ocaml , therefore inheriting of design decisions ocaml's 25-year old history of being natively compiled language little regard strange javascript niche on web.
but think biggest trade-off between reasonml's sound , flexible type system, , typescript's ability "sneak" comprehensive static checks existing javascript code base.
typescript's type systems explicitly designed not sound, , while give hand of time, won't able give many guarantees. can't trust type system have back, 1 biggest advantages of having proper static type system.
typescript limited decision of avoiding runtime type information, necessary features such pattern matching , major benefit of working typed data in reasonml.
reasonml on other hand requires boundary between , existing javascript code explicitly defined. types can extent inferred, must still determined @ compile-time. makes javascript interoperation more laborious, if boundary gradually moves existing javascript code base converted. it's not obvious how type of weird stuff goes on in javascript, it's possible, , temporary until has been converted reasonml anyway :)
obviously i'm biased, hope doesn't come across picking clear winner @ least because there isn't. major trade-off, @ least long world's not perfect.
Comments
Post a Comment