A live stream where Sean shows John what it takes to port Reason to JavaScript
Not having watched the full video, please forgive me if this is a stupid question, but... why would you want to switch from Reason to JavaScript (our Typescript)?
Yours truly, A person who is learning Reason to get away from JS/TS (for code safety and improved language ergonomics)
Good question! We mention it in the video but:
We built a proof-of-concept of the Egghead transcript editor (e.g. https://eggy.netlify.com/courses/shareable-custom-hooks-in-react) in Reason because that's by far the fastest way for us to prototype and build.
But the initial plan was to hand it off to the Egghead folks to maintain, and it's not fair for us to force Reason on them if they didn't ask for it. So we agreed ahead of time that we'd convert it to JavaScript if they decided to use it, so that their team could hit the ground running maintaining it.
It's also an interesting experience (I've only ever gone the other way, converting JavaScript to Reason) to mechanically translate the code in such a way where you don't break assumptions. Reason helps a ton with even that!