News for hackers. Stuff that matters.
Re:CSS WG resolved to officially work on native custom funct... by ahmedfromtunis on Tuesday February 13, 2024 @11:42AM (#39359541)
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/...?

Re:CSS WG resolved to officially work on native custom funct... by lioeters on Tuesday February 13, 2024 @12:02PM (#39359837)
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.

Re:CSS WG resolved to officially work on native custom funct... by cqqxo4zV46cp on Tuesday February 13, 2024 @01:42PM (#39361138)
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.
Re:CSS WG resolved to officially work on native custom funct... by thr33 on Tuesday February 13, 2024 @05:35PM (#39363802)
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.