So I thought about this a bit more and have some technical feedback, even though it's beyond the scope of this post. If I apply this pattern more than once, do I have completely separate elm programs that live in different parts of my js app? What if they need to share code, e.g. model definitions? Do I have to send multiple copies of the core library down the wire? Do I commit the compiled Elm to git?
My ideal tooling here, and I suspect that NRI has some of this already, would allow multiple Elm projects to be built, linking against one copy of common code (core, model defs, 3rd part libs). It would tie into Rail's asset pipeline to recompile on page load or file change in development and precompile in production. If we're serious that this is the success story, than we should write tooling to that story. The compiler is still built around an entirely elm website. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
