undefined | Better HN

0 pointstalmand11y ago0 comments

If you are bad at CSS and good at JS then this tool will not really help you. In the end it generates CSS, which you have to know to some degree to be able to create the JS version of it.

I agree on the complexity issue with the examples, I don't see how the 30% savings claim would hold up.

0 comments

3 comments · 1 top-level

oleg00911y ago· 2 in thread

saving come from 1. code reuse. less/stylus will generate everything dozens of times 2. vendor prefixes are added effectively at runtime

talmandOP11y ago

CSS allows for code reuse, it always has. It's called cascading and classes.

Preprocessors will generate bloated CSS if not coded properly, same as it's possible to hand-code bloated CSS.

There are libraries that generate vendor prefixes at run time. If prefixes are really a bother (they're not as much anymore) then preprocessors and other compiling tools have solutions for that as well. Which will be more efficient for the browser.

oleg00911y ago

1. Stop assuming I am stupid.

2. I know code reuse technics in css, they are mentioned in the presentation. Cascades do not work for component based development. Adding multiple classes to an element leads to awkward code and also will lead to namespace conflicts if you don't name everything very specifically.

3. Vendor prefixes are there and will be used for new features too. They will not go away. Precompilers can't avoid generating all prefixed variants.

j / k navigate · click thread line to collapse