Languages, Theory and other Fun Stuff
I’ve created a library, which I lovlingly refer to as Haskelm. It uses TemplateHaskell to read Haskell source and translate it into Elm code, which can be compiled and run in the browser. The library also automatically generates the Elm code to convert JSON objects to ADTs using the same scheme as Haskell’s Aeson.TemplateHaskell.
You see the package on hackage or github. It as a Haskell library, embedding Elm source in Haskell code at compile-time using Template Haskell. It also contains an executable, which reads Haskell source from stdin and outputs Elm on stdout.
I see two main uses for this. The first is having unified algebraic data types between the front and backend of a server. This would allow you to use Yesod, Happstack or Snap as your web framework, but write your interface in Elm.
The second is to allow for the fast porting of Haskell libraries to Elm. This should allow the Elm ecosystem to grow quickly, and packages to be developed easily.