2 ms·

Can someone explain this crazy decision ? It makes no sense at all. This is the web framework library that implements their official and public UI design langua

Can someone explain this crazy decision ? It makes no sense at all. This is the web framework library that implements their official and public UI design language using formal web standards. Why in heaven's name would this go into "maintenance mode" ? Do they not want people making web-apps using Material Design anymore ? I thought the Chrome team was all gung-ho on web-components and shadow DOM as the one true, standards-compliant way of developing web-apps.

spankalee 2y ago
The Chrome team is indeed building all their web UI (things like settings and bookmarks) with web components and... Material Web Components! Chrome OS is also building most or all of their built-in apps this way. They are pretty put out by this decision, and will have to maintain Material components themselves, but the Material Design team doesn't prioritize Chrome as a customer - the VPs weren't graded on helping them for some reason.