Stable style API?

[cristianoccazinsp]

Hello,

I really appreciate the work and effort put into this library. I've been using it since version 1 (I think), and it has always been great. However, you guys keep changing the styling API on every version! I don't know how many times I had to do massive code migrations in order to keep up with the updates, yet every new version introduces a million breaking changes.

Are you guys ever going to stay with a stable API? Every update is dreadful, so many breaking changes. Version 4 withStyles and makeStyles is great, flexible, and very easy to understand. Version 5 styling solution seems more complicated and difficult to use, not to mention the code refactor to migrate to it is huge! Are you guys sure you won't change it yet again in version 6?

Not a complaint, just wanted to know the rationale behind so many breaking changes on every version.

[eps1lon]

Thanks for the feedback.

Breaking changes are not taken lightly. We usually have a strong rationale for larger breaking changes or easy migration paths (e.g. codemod) for smaller breaking changes. All of these breaking changes are described in our migration guide and announced in advance in #20012 (which is also pinned in this repository).

Are you guys ever going to stay with a stable API?

Like everything else, the web advances over time and better solution for older problems (or even new problems) are discovered. Sometimes these new solutions require breaking changes. Every breaking change should improve the library overall. If you want to focus on stability then you can always stay on the current version. These versions are not removed from the web.

Not a complaint, just wanted to know the rationale behind so many breaking changes on every version.

The rationale is described in detail in #22342

Closing since the discussion should either happen in #20012 or #22342