I am Richard Feldman, author of Elm in Action and instructor of the Frontend Masters Elm Workshop. The main open-source projects I'm working on right now are elm-test and elm-css.
I work at NoRedInk, where we have 80,000 lines of Elm code in production. We introduced Elm in 2015, and since then our production Elm code has thrown a total of zero runtime exceptions. We hired Elm creator Evan Czaplicki in 2015 to continue developing the language, and we're hiring!
I'll be here until noon Pacific Time. Ask Me Anything!
Latest comments (119)
elm‐in‐action.com/folders/list
This link from your book doesnt work anymore. Chapter 7
Hi Richard!
I have used the Real World Elm demo as the basis of a project I am working on. So far it is working out really well, and I am happy with the structure and flow of the code.
The one area where I am struggling is providing application authentication. The demo provides authentication between the front-end and back-end, however, I need to protect enforce authentication at the front-end elm level.
How would you recommend handling this? Do you have demo code available that provides this type of authentication and routing?
Thanks,
Peter
I like to learn Elm, what are the basics things I need to know to get the good grip of the language?
When will Elm support Node (or be usable in the backend)? In the backend, what has the best affinity with Elm right now?
What is the most difficult part about switching 100% to ELM?
Have you thought about going back to JS at some point (at least for an specific project)? I mean, maybe something was really complex/troublesome to build in ELM instead of Js?
Thank you!
Legacy code - there's rarely a good justification to porting really old code that doesn't get used anymore. (So we haven't really done it!)
Only for Node stuff, as Elm is only built for browsers right now.
For browsers, it's the opposite: I don't think I can ever go back. I can't predict the future or anything, but right now I have a really hard time seeing myself applying for a JS job ever again.
That was super quick!
Thanks Richard and thanks for pushing ELM forward <3
what is the meaning of life?
Hi, Richard!
What in your opinion are most fundamental problems that modern front-end community is trying to solve right now?
Is Elm involved into this problem solving?
Thank you!
Love Elm, keep up the great work folks!
When do you plan to finish the book (I am surprised no one asked yet, or have I missed it?)
Any advice for a team looking to incorporate Elm into a large React-based app who relies heavily on server side rendering (SSR) in Node? In a similar vein, do you have thoughts on apps that are SSR'd vs apps that are single page applications?
See dev.to/rtfeldman/i-am-the-author-o... regarding SSR in Elm.
My thoughts on SSR in general are "don't do extra work unless it's going to solve a problem you have." 😄
The blog post for Elm 0.17 mentions: "Generated JS is smaller and works with Google's Closure Compiler"
Do you have any experience/numbers on this? Do you know if Google's Closure Compiler is superior for making Elm's JS small (compared to UglifyJS, for example)?
Yeah, I don't have any personal experience comparing them. Sorry!
At NRI, this isn't really a concern or issue. We don't use Closure compiler, and we currently don't need to. There's a bunch of posts on the mailing list about this though -> groups.google.com/forum/#!searchin... and groups.google.com/forum/#!searchin...
Are there plans to move away from Javascript for Native code? If so, could you speculate on what Elm would look like post-JS?
Thanks!
What Noah said. 😄
There is definitely no solid plans for that. WebAssembly gets brought up and that might be a good idea one day but right now it's definitely not.
What's the most unusual thing you've ever seen Elm used to do?
Pretty sure I saw someone (and I think it was you, but I could be misremembering) write Elm code to control a synthesizer!
congrats for the book! God bless you and guide You!
Thank you! So nice of you to say! ❤️