On the other hand, Elm type system is limited and we can’t express our domain through it. Our apps deal with complex information and we’d like to have more tools at our disposal than records and tagged sums. We’d like to enforce laws and relations between data, even if we need to pay with steeper learning curve.
- I am curios what kind of things Elm cannot express about your domain. Is it things like dependent types?
- What tools does TS give you that Elm does not in modelling data?
I am asking this because I have always, with no exception, found it much simpler and practical to model complex models in Elm rather than TS. So much so that I often start to model something in Elm only to get clarity on how to properly do it in TS, and this often requires a bunch of helper types/libraries to do right.
To tie it back to the thread’s topic, if it happens that the project I work on moves away from Elm, I could not see how data modelling is the reason for that. I am curious to learn how that happened to you.