(no title)
AltruisticGapHN | 1 year ago
Sass and BEM methodology works fantastically well. Naming things isn't that hard, but Tailwind/utility approach is also extremely useful.
Those new features, besides container queries is just gibberish. Layer? WTF? The cascade is bad enough as it is, most devs can't even deal with the cascade it's why Tailwind become so popular. And we should dive even deeper into the cascade BS with layers and scoping and whatnpt? Again, this all looks like it was made to be output by some CSS compilers, not written by a developer.
willio58|1 year ago
At the end of the day these are all more tools in our toolbelt. If you want you can keep writing CSS the same way you always have.
culi|1 year ago
I don't really stand by GP's comment but I also don't think their concern can be dismissed this easily. We generally write CSS as teams. You'll have to read as much CSS as you'll have to write. Ideally you actually read more than you write so you can reuse existing rules and follow established patterns
Anyone writing CSS for a day-job, an OS project, or even just following a tutorial will have to at least familiarize themselves with these concepts
paulryanrogers|1 year ago
JimDabell|1 year ago
paulddraper|1 year ago
I think the syntax is good (getting better with nested selectors)
AltruisticGapHN|1 year ago
Maybe in 10 years time we’ll finally get to what sass can already do today.
notRobot|1 year ago
pipeline_peak|1 year ago
cthor|1 year ago
An ideal version of CSS would remove the need for SASS, BEM, and any non-thematic framework. That we have to use those right now is a problem to be fixed.