@abraxas
Any webdevs in here want to make the need for Sass to make sense to me? It doesn't expand CSS, and browsers can't even render it - you have to compile it back to CSS to include in your project. It also seems to discourage multi-classing elements... It means that any adjustments you need to make will be done to the sass and then converted back to css. Sure it only takes a second, but still. It also means that the output is somewhat of a generative mess. Am I doing some digital-boomer shit by complaining about this? Am I basically yelling at the kids to get off my vLawn? Am I out of touch, or is it the kids who are wrong? LOL
4 comments
I feel this 100% even if I did not do some work in this field for 5 years. Why reinvent the wheel when it slows down the car...
I get why we'd want improvements to web dev, but this stuff is just stapling pretty "fixes" to 40 year old foundations. At some point you need to just accept that the tech has progressed beyond its original vision and needs to be re-invented at its roots.
The next gen might be made by the AI. Coding and browsers, started at 0. Who knows. But I'd still like to understand the code and that's impossible then.
With AI where it is right now, I hope not lol.