Oh dear. >> Elm promised to offer a nicer interface to creating web apps and isolate people from the insanity of HTML/CSS/JS
This is exactly why I chose to go with Elm a couple months ago. I had no interest in becoming enough of an expert on HTML/CSS/JS to do a complex animated game in them. See what I have done in Elm here: deepfinesse.com/demo. It's been a total joy implementing this in Elm, learning as I go. But now I seem to have hit several show stoppers. I chose to implement using Graphics.* not Html.*. At first, the paradigm shift in 0.17 presented no problems, my app ported over easily. But now: 1. Lack of Touch.* means no smart phone support (partially solved, see separate post) 2. Animations even when idle burn 100% CPU causing complaints of laptop fans going beserk (see separate post) 3. No Graphics.Input I've been woken up to this last one by this thread. I haven't added it yet, but I do need a way for users to enter new deals to analyze and play through. Usually this would just be a cut&paste job of a text description of a deal but also one could type into it manually, something like this describes a bridge hand: 7.9.A987642.9863 96.T852.KT.AKJ52 AKQJ8542.AKJ..T7 T3.Q7643.QJ53.Q4 I suppose all 3 issues means I will need to bite the bullet and convert everything over to Html.*? On Wednesday, July 6, 2016 at 7:46:27 PM UTC-4, Evan wrote: > > *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.
