"Code is the easy part" First you need to figure out what exactly the Elm community wants and needs. Once you have a pretty good idea of that, you can start pr

"Code is the easy part" First you need to figure out what exactly the Elm community wants and needs. Once you have a pretty good idea of that, you can start prototyping things. Elm is still young, and the most pressing concerns for using Elm in production is not the lack of interfaces/protocols/typeclasses, but stuff like debuggers, which is what Evan is working on. I'm sure we'll see some tool for ad-hoc polymorphism in the future, but not in the short term.