Future of this library

Hi everyone,
motivated by the recent talk on [when and how to use web components](https://www.youtube.com/watch?v=tyFe9Pw6TVE) by @lukewestby, I have been thinking about the future of this library. My thoughts are currently as follows:

- It seems the Elm community would favor a web components approach to UI libraries, and I think that makes a lot of sense. The effort of both elm-mdl and elm-mdc stemmed from the (incorrect*) assumption that web components would not be feasible in Elm.

- I have started and will continue to experiment with [material-components-web-components](https://github.com/material-components/material-components-web-components), the official implementation of MDC Web via web components and that approach seems to be very promising. You can check out the in-progress version [here](https://github.com/aforemny/elm-mwc).

- It seems that both web components and material-components-web-components is still very much a work-in-progress. However, it seems that both technology could be accessible, within the next.. months?

- I have just bumped the supported version of this library to v0.37.1, and I do plan to maintain this library until elm-mwc is a mature replacement. I am considering to update the version of MDC Web less frequently. I am questioning however, if I should release this library on package.elm-lang.org at all.

- Whilst experimenting with elm-mwc, I will try to come up with a better API for components. Feel free to join the discussion when it is that time.

As always, there are no promises contained in the above statement.
Any feedback would be appreciated. :-)

*=pending any unforeseen obstacles