3 ms·
One of my worst decisions as a developer was to build upon a component framework maintained by Google. Material Components for the web is constantly introducin
by dessant 6y ago
One of my worst decisions as a developer was to build upon a component framework maintained by Google.
Material Components for the web is constantly introducing breaking changes that make building upon the framework a nightmare. Lately they've even set this expectation in the project description. The problem is that the components are rather buggy, so you must regularly update them to have upstream bugs fixed.
> Material Components Web tends to release breaking changes on a monthly basis, but follows semver so you can control when you incorporate them. We typically follow a 2-week release schedule which includes one major release per month with breaking changes, and intermediate patch releases with bug fixes.
https://github.com/material-components/material-components-web https://github.com/material-components/material-components-w...
The development team's decisions have been questionable [1][2][3], so consider this a warning in case you are tempted to use the project.
[1] https://github.com/material-components/material-components-web/issues/4799#issuecomment-551537015 https://github.com/material-components/material-components-w...
[2] https://github.com/material-components/material-components-web/issues/2865 https://github.com/material-components/material-components-w...
[3] https://github.com/material-components/material-components-web/issues/2639 https://github.com/material-components/material-components-w...
- Tyr42 6y agoI feel like the breaking changes must be because they're used to working in a monorepo, where you can just change the code and the clients at once. No need to worry about compatibility