CSS WG level 4 and 5 module changes due to misuse of !important with layer which while not illogical as a solution to external frameworks causing language fragmentation and rushing solutions instead of collaborative, evolving WG specs is reactionary, not innovative. Bothers me.

But it also gives first-class control to the developer when using third-party components and libraries.

As a dev who is often hired to work on Bootstrap-born (or other third-party libs/components) sites after the fact (and who knows the cascade and inheritance), I no longer have to mimic the stupid-long selector I need to override.

I understand that especially when you have large sites with multiple origin CSS that has enough conflicts to take so much extra time to resolve without the CSS important declaration. Also common in Legacy that is not portable in any way and should be easily portable if it is web.