The biggest problems with Elm for me was (and maybe are): - What is tagged type and how and why to use it. - Cmd, Msg, Task, Subscription, effects - translation for a JS developer, please. - SPA routing (still a pain for something little more complex than "hello world") - Where is my UI components? (Reusing code, cross-component and child -parent communication) - Http, Json, store responses and errors (before and after RemoteData package)
On Monday, 24 April 2017 16:06:53 UTC+2, Jeff Schomay wrote: > > Hello, > > I am considering doing some training material on working with Elm in > production. I want to focus on areas that people struggle with after they > are already familiar with Elm. What concepts continue to confuse you? > What product requirements have been difficult to achieve with Elm? What > is most painful about your Elm codebase? > > Some topics I have already thought of: > > - decoders > - debouncing (http autocomplete input field for example) > - scroll to element > - testing > - unwieldy update functions > - api design > > If you have anything you'd like me to consider, please add it to the list. > Thank you! > -- 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.
