The best parts of it seem to be its compiler (performance and dead branch trimming of compiled code). Otherwise, it looks like a similar machination to Angular 1. (HTML-based templates, mustaches, two-way binding, directives).
Component-orientedness = object-orientedness. The same refactoring problems with mutable state and effectful functions still apply. Elm isn't component-resistant just to be dogmatic about FP. It's actually providing a large maintainability advantage (with immutable data and pure functions) that happens to make it hard to do stateful components. Beyond a low-level tricks they might be using, I doubt the compiler can be generalized to other compile-to-JS languages, as it will be expecting Svelt framework sprinkles. On Wednesday, November 30, 2016 at 12:01:27 PM UTC-6, Duane Johnson wrote: > > There's been some ongoing discussion about components (web components, > simplifying design with component re-use, etc.) and I saw this introduction > to Svelte today: > > https://svelte.technology/blog/frameworks-without-the-framework/ > > It seems like a compiler that produces bare-metal components by separating > data from rendering. There may be some compatibility with Elm if it is > possible to let Elm control the data and leave the rendering to Svelte. > > Has anyone taken a look at it yet? > > Duane > -- 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.
