*DRAFT - Do not share the npm package or draft blog post yet!* Embedding Elm in some big JavaScript project is not very hard, but I think you currently need quite a lot of experience with Elm for this to be obvious. It's like three lines of JS, but you typically learn those lines pretty late.
So I created react-elm-components <https://www.npmjs.com/package/react-elm-components> to make it much more obvious. In addition, I drafted a blog post called How to Use Elm at Work <https://dl.dropboxusercontent.com/u/4542162/how-to-use-elm-at-work.pdf> that outlines the typical success story I hear from people that introduced Elm successfully. Let me know what you think! I am planning to announce both of these things on Monday, so *please do not share react-elm-components or the blog post before then*! It is cool to talk about it in Elm community forums of course, but please not on Twitter, Reddit, HN, etc! Context I released keyed HTML nodes <https://groups.google.com/forum/#!topic/elm-dev/V0HaGgjQHW4> last week. This was the final technical hurdle blocking a blog post about the performance improvements in elm-lang/html. It is much faster than a lot of things! As I drafted *that* blog post, I realized it would be helpful to publish "How to Use Elm at Work" first. I hope that "Elm is faster than X" will get a decent group of people interested in giving it a shot, so I want to make the next steps as clear as possible! -- 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 elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
