Richard Feldman Discusses Elm and How It Compares to React.js for Front-end Programming
Published April 28, 2017
39 min
    Add to queue
    Copy URL
    Show notes
    Why listen to this podcast: - Using a compiler to catch errors at compile time instead of at runtime means much easier refactoring of code. - Incrementally replacing small parts of an existing JavaScript application with Elm is a safer strategy than trying to write an entirely new application in Elm - Elm packages are semantically versioned and gated by the publishing process, so minor versions cannot remove functionality without bumping the major version. - The UI in an Elm application results in messages that transform the immutable state of the application; this allows a debugger to view the state transitions and the messages that triggered them, including record and replay of those messages. - Elm has been benchmarked as being faster than Angular and React whilst being smaller code, which is attributed to the immutable state and pure functional elements. More on this: Quick scan our curated show notes on InfoQ You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. Subscribe: Like InfoQ on Facebook: Follow on Twitter: Follow on LinkedIn: Want to see extented shownotes? Check the landing page on InfoQ:
        0:00:00 / 0:00:00