The more time I spend with #Javascript Framework code, the more I am convinced the devolution and/or dislike of the #CSS Cascade makes sense. Whether it's building an entire application interface or a standalone app or a one-size "responsive" plug n' play app/site I'm seeing why.
2
5
7
If one views source derived from a #Javascript #Framework and opens a current in-browser dev tool, the #CSS is a godawful confusing mess! It is logical to just want to override conflicts in style with inline styles and/or !important. Educators may be looking at it backward. Me.
Jun 8, 2020 · 11:13 PM UTC
1
3
Instead of explaining the browser sort first, if we start with the most specific rule (Specificity algorithm) we end up with an actual #CSS rule that regardless of origin will apply given we follow (I'm almost sure) likely no more than 3 steps and two exceptions empowering devs.
2
3
The conclusion to this theory of how to tap back into the power of the cascade results in far less #CSS far less confusion far more elegant code and far less obfuscation. It also reveals that our tools have become part of that obfuscation and resulted in over complex processes.
3