3 ms·

I think it comes down to one of two things; the first is ignorance. If the only tool you have is a hammer, everything starts to look like a nail. If you only kn

by sbacic 5y ago

I think it comes down to one of two things; the first is ignorance. If the only tool you have is a hammer, everything starts to look like a nail. If you only know about React and Sass, any layer beneath that is a complete mystery and not something you'd even consider as a solution because you're not aware of it. The second, and my preferred theory, is that the modern web stack has not adequately followed increasing user requirements, forcing us to take much longer to develop what seems like trivial new features. It's not that i18n, or larger images or maintaining state in the browser is some huge, insurmountable problem that can't be solved. It's just that our tools are so woefully immature that we spend more time wrestling with them than we do actually working on the features we're being paid to work on. And for what? For some vague illusion of choice that for the vast majority of people doesn't even matter? I don't care if I use Redux or one of the bazillion different variations on the idea. Ditto for Sass, Tailwind or what have you. The web layer needs to solidify already, give us a decent bedrock to build our apps and websites on and just get out of the way.

schwartzworld 5y ago
I don't think SASS/LESS/SCSS fall in the same category at all. The ability to nest selectors alone makes stylesheets more readable and easier to work on. If the rest of the team likes SASS but you don't, because I guess you are a masochist, you can just write regular CSS without using the SASS features. Plus sass is a dev dependency. Even if my team wasn't using it, I could write SASS on my machine and compile before committing the code.
- sbacic 5y ago
  Half of the modern web stack is there because it makes development <INSERT POSITIVE ADJECTIVE> to work with. The problem isn't SASS per se, it's that we have half a dozen tools with overlapping functionality because we can't nest CSS selectors (or some other, fairly trivial benefit) with no clear, overwhelming winner out of the lot of them so we have to know all of them. And then we have highbrowed discussions over which one is better for a particular project (hint: it doesn't really matter). I just wish we'd settle on one, _finally_ solidify the web layer and get on with doing productive work.

by sbacic 5y ago

schwartzworld 5y ago

I don't think SASS/LESS/SCSS fall in the same category at all. The ability to nest selectors alone makes stylesheets more readable and easier to work on. If the rest of the team likes SASS but you don't, because I guess you are a masochist, you can just write regular CSS without using the SASS features. Plus sass is a dev dependency. Even if my team wasn't using it, I could write SASS on my machine and compile before committing the code.

sbacic 5y ago
Half of the modern web stack is there because it makes development <INSERT POSITIVE ADJECTIVE> to work with. The problem isn't SASS per se, it's that we have half a dozen tools with overlapping functionality because we can't nest CSS selectors (or some other, fairly trivial benefit) with no clear, overwhelming winner out of the lot of them so we have to know all of them. And then we have highbrowed discussions over which one is better for a particular project (hint: it doesn't really matter). I just wish we'd settle on one, _finally_ solidify the web layer and get on with doing productive work.