I wrote up an introduction to using Web Components and Polymer with Elm. I just realized I hadn't posted this here, and since the recent thread about components came about it seemed reasonable. Here it is:
https://www.dailydrip.com/topics/elm/drips/web-components-introduction I've been using this in a project and it's honestly really enjoyable. I also realized after the fact that this one post comes off sounding kind of down on elm-mdl in a way that I didn't intend - in the next one I go on to implement a layout using polymer, and while it's really nice and works very well, it's nowhere near as simple as doing the same thing with elm-mdl. I kind of think that having an elm-mdl (but probably broken out as `elm-paper` and `elm-polymer-app` and `elm-iron`) that takes what elm-mdl has done and applies it to the use of these web components might be awesome (with corresponding suggestions on installing them properly, and potentially with the dev-mode easy-setup that something like elm-mdl's `Material.Scheme.topWithScheme` provides - knowing that it's no good for production but makes dev easier). I was very skeptical that it would be great, but I find myself actually loving this. In the larger project using it it's been a blast to get the benefits of elm while still being able to 'be part of' the larger web components ecosystem. Tacking on some type-niceties to make it easier to use the components correctly would be extra nice, I think. I haven't yet done a full build, but I don't actually have the worries I once did about the resulting bundle size either (this might be misguided!) Anyway, what do you think? -- 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 elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
