On Wed, Apr 26, 2017 at 5:17 AM, John Orford <[email protected]> wrote:
> My 2c on above... > > 1) web components - once they're a standard they will be a must. > > Perhaps they feel like a necessity now (I am sold) but they're still in a > flux, browsers support bits and pieces, some things haven't been finalised > yet. > V1 has been accepted and assumed by the major browser providers for some time and we will probably see official support in the evergreens this summer but this is beside the point. The idea of custom elements could have been implemented in Elm without browser support if this would have been desired. Unfortunately, this idea comes packaged together with the idea of localized state and this seams to be rejected on philosophical grounds. I seriously doubt we'll ever see web-components support without a proper dialog around this subject. I've seen the idea of "mutation-as-service" being put forth as the main drawback of web-components and I would love to see a proof-of-concept for this just so that I can accept that this is a bad idea. Heck, I even tried to implement such a proof-of-concept and failed. Anyway... I used to feel worse about this topic but I realized that there are still a lot of things that I can do and haven't done yet so... I have options. -- There is NO FATE, we are the creators. blog: http://damoc.ro/ -- 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.
