1. 13
    1. 4

      This is great news for me! I’ve been waiting for somewhere to take my project that is stuck on Elm 0.18, and hoping that Rescript plus its ecosystem would mature to that point. Thanks for sharing!

      1. 3

        Funnily enough, the Elm 18 to 19 transition is what caused us to move to Rescript too.

        Have you seen Philip2? https://blog.darklang.com/philip2-an-elm-to-reasonml-compiler/

        1. 2

          Yeah, we had some conversation about this at the time. But at that point there was a ton of churn in the bucklescript space, and reasonml/Rescript has seemed much more focused on React, so I didn’t make a move yet.

      2. 1

        Will the legend of i18n woes continue?

        1. 3

          :-) Rescript has plenty of escape hatches and is easy to bind to browser APIs. My woes are much more likely to be self inflicted and I’ll keep them to myself!

        2. 2

          I’m not familiar with the woes - can you provide context?

            1. 1

              Ah, yes, rescript shouldn’t have the Native code issues, it’s very easy to write wrappers to JS functions, and many libraries wrap JS libraries and provide rescript-y APIs to them.