Must admit I was maybe expecting slightly more detail in how Reason / OCaml's rules help avoids these shortcomings - felt like the end came abruptly just as I was getting into it.
Great writeup overall though - very informative about the shortcomings of TypeScript for someone coming from the Reason side having not played around with TypeScript enough. People have said that TypeScript is unsound and now I understand a bit more as to why. Thanks!
Programming languages enthusiast. Author of Learn Type Driven Development: https://www.packtpub.com/application-development/learn-type-driven-development
Thanks! :-) I think you're right, I could probably have written a bit more about specifically Reason/OCaml type system that prevents lots of implicit errors from happening like they would in JS/TS. I'll try to come up with something for a future post.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great post!
Must admit I was maybe expecting slightly more detail in how Reason / OCaml's rules help avoids these shortcomings - felt like the end came abruptly just as I was getting into it.
Great writeup overall though - very informative about the shortcomings of TypeScript for someone coming from the Reason side having not played around with TypeScript enough. People have said that TypeScript is unsound and now I understand a bit more as to why. Thanks!
Thanks! :-) I think you're right, I could probably have written a bit more about specifically Reason/OCaml type system that prevents lots of implicit errors from happening like they would in JS/TS. I'll try to come up with something for a future post.