Careswitch embraces ReScript
We're really excited to announce that Careswitch is embracing the ReScript programming language and community to build out its next generation platform of home care products and applications. If working with a new programming language and paradigm to improve the lives of family members and caregivers sounds interesting to you, we are hiring.
As a company that has previously embraced TypeScript React across web and native development, we felt it was important to clearly understand the differences and tradeoffs between TypeScript and ReScript. Going into the evaluation we had convictions around a couple of items:
- Long-term maintainability was at least just as important as short-term productivity and velocity—we couldn’t easily justify another major refactor or rewrite: the only way to go fast, is to go well.
- We wanted to continue to leverage React across web and native to tap into the rich ecosystem of libraries and tools, as well as conserve most of our runtime intuitions around component hierarchies, flow of state, and the React rendering model in general. (You can make an argument that React is based on other, possibly superior architectures. Ultimately, we decided that the greatest improvements we could make were to the static build-time aspect of development, not so much the runtime).
At the end of our evaluation, we ended up making the decision to go with ReScript based on 2 main reasons:
We will dedicate another blog post in the future that will dive into the details of ReScript and how we’re adopting it at Careswitch to build and ship products. We will also discuss our plans to contribute back to the community, starting off with maintaining and publishing bindings that will allow other ReScript engineers to interop with existing JS libraries we use such as Headless UI, Luxon, and Next.js. We’re thrilled to be joining a fantastic community of companies and engineers working to build functional yet pragmatic applications that dare to have your cake and eat it too.