Hacker News Reader

Comment by karaterobot | Hacker News Reader

The market has already spoken: people want a better developer experience with CSS. At this point, if you're working on a non-trivial app, you're either using some CSS-in-JS solution, or using a pre-processor, but you're probably not just writing CSS directly. The specification should include the things we know people already need to work with it.

The question is how will it be implemented. Personally, I always greatly preferred Stylus' approach, and never understood why Sass was so well liked. If the CSS-WG doesn't come up with its own weird syntax, it'll probably be something like Sass, which will be fine I guess.

View on HN

I think its due to Ruby on Rails, when Ruby SASS was a thing, it was around the same time of "Peak Rails" (mindshare wise certainly) and was used as part of the provided build pipeline.

That, more than anything, popularized SASS in my mind

Yeah! Ruby Sass was my first exposure to CSS preprocessing. Such an improvement at the time. I used it for a decade. Then some intern at a company I was working for said, "y'all tried Stylus?" and within about 10 minutes I was converted. But, not everybody had that experience I guess.

I work on a fairly complex application, and use neither of those.

Besides, why would the specification for CSS take into consideration anything that's not pure CSS. Do JS maintainers take into consideration that people are transpiling javascript from typescript/dart/...?

The ECMAScript standard did consider transpiled languages - for example, by incorporating concepts from CoffeeScript like classes, destructuring, arrow functions. For sure they're considering ideas from TypeScript.

I'd imagine some advances in the CSS specs are influenced by concepts from traspiled languages such as Sass, for example, variables and nested selectors.

I don’t follow this logic at all. An idea can be rained by virtue of it first being included in a preprocessor? postcss would like to have a word.

was just thinking this. work on a variety of complex webapps across multiple frameworks and you'd never catch me dead using css-in-js or a preprocessor.

Reply on news.ycombinator.com