What about the other stories? To folks saying, this seems too one-size-fits-all, I have not heard another story. I have seen people *try* other paths. They don't work though. So I'd love for there to be other paths, but I have not heard of another one.
Now, it is true that if you are a consultant under specific circumstances or the only engineer on a project, you can do things a different way. I think these stories are the outlier though, and I think the general outline of the story here still applies to them. They just skip the "help everyone learn" phase. I feel like I emphasize this appropriately in the post though. Many Components Yesterday I added a section about "what to do the second time" that suggests growing your component or doing something more ambitious on a separate page. I can't tell if people are reacting to the most recent blog or the commentary on old versions, but I think the "embed 90 things and be sad" route is a plausible mistake, so I'll make it more explicit. Okay, thanks for the feedback! I gotta write a bunch of other posts too, so I will make edits and things will go live on Monday. On Fri, Jul 8, 2016 at 10:42 AM, Yosuke Torii <[email protected]> wrote: > Looks great. However, I also agree with what other folks have mentioned. > > Multiple Elm components in one app needs large copy of common code. I > think providing a core library like "elm-runtime.js" would be helpful, for > sharing code and enabling browser cache (maybe using it via CDN?). React + > Elm is already heavy especially considering mobile apps (not sure mobile > apps are the target of Elm though). Also, some people find value in server > side rendering which React supports and Elm doesn't. > > IMHO, the title "How to use Elm at Work" sounds like estimating the > reasons for not using Elm in production too small. For reasons like "I love > Elm but my manager does not allow adopting it" or "I don't have enough > confidence to introduce Elm in a large legacy code", this post is super > great. I strongly agree with everything mentioned in "The checklist". > > Please don't take this wrong way. I don't mean to say "Elm should support > all these features". Just thinking how to tell things the best way. > > > 2016年7月7日木曜日 8時46分27秒 UTC+9 Evan: > >> *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 [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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.
