A person has created a link of CSS nesting rules, and CSS developers are thrilled with it. For a long time, CSS has been a sort of Wild West in its lack of coherence and standardization. Developers tend to be people who like a structure to follow. They are logical in their thinking patterns. While most developers do have a sense of creativity, they need a foundation upon which to be creative. A set of rules for CSS nesting is a great start.
Many coders who use CSS chimed on on what they thought of the first iteration of CSS nesting rules. They noted that combining CSS with other coding techniques requires the use of rules from those other languages, so a lack of standardization in some parts of CSS is not a problem that every coder deals with on a regular basis. These coders also noted that standardization is different based on the approach to CSS. Grid is rather regimented, while global is less so.
Some people did not even know what CSS nesting rules meant. They were used to just coding in a way that they assumed would make sense to everybody who looked at it. One such person asked for an example and gave a line of how they would write their CSS code. A person who likes nesting rules commented back with how the nesting rules would apply to that person's CSS coding. The original person appreciated the example.
A few people wondered why there needs to be any nesting rules at all. A wise and experienced coder noted that in a complex coding schema, a lot of elements and attributes with different sets and subsets could be confusing to follow. Being able to nest all of it would look neater and facilitate following the path.
A couple of readers thought that nesting was going away in favor of the BEM approach to CSS coding. Others commented back that the two approaches are both in use and neither of them is likely to go away. Coders should be open to the idea of nesting for clarity. For more information click here https://www.reddit.com/r/web_design/comments/aze38b/css_nesting_has_entered_stage_1/.