reasonml <3
I'm only guessing that's because you have prior experience with Ember and are only starting to use react now. I find code written in ReasonML is 100x more maintainable than anything written in javascript, whether it's…
Similar to flow. JS interop is great, so you can literally change bit by bit and refactor from the inside out.
Also for your issue with deeply nested options, have a look at this https://medium.com/w3reality/working-with-option-using-maybe...
Since moving from javascript to reason/ocaml, i'm genuinely nervous about refactoring Js now. Helpful compiler errors are literally life changing, and being able to handle options with Some/None means no more nasty…
You forgot the best bit... variants and pattern matching!
I thought this and was put off at first, but have come to the conclusion that you really don't need redux (I've used it thoroughly for years). We've been converting a large JS react app to Reason, and strongly typed…
reasonml <3
I'm only guessing that's because you have prior experience with Ember and are only starting to use react now. I find code written in ReasonML is 100x more maintainable than anything written in javascript, whether it's…
Similar to flow. JS interop is great, so you can literally change bit by bit and refactor from the inside out.
Also for your issue with deeply nested options, have a look at this https://medium.com/w3reality/working-with-option-using-maybe...
Since moving from javascript to reason/ocaml, i'm genuinely nervous about refactoring Js now. Helpful compiler errors are literally life changing, and being able to handle options with Some/None means no more nasty…
You forgot the best bit... variants and pattern matching!
I thought this and was put off at first, but have come to the conclusion that you really don't need redux (I've used it thoroughly for years). We've been converting a large JS react app to Reason, and strongly typed…