Re:What's new in CSS4
by alexchamberlain on Thursday October 27, 2011 @06:48AM
(#3162441)
Why slow down CSS with constructs that can be achieved by prior compilation and a few Makefiles?
[ Parent
| on HN ]
Why require adding a fiddly and complex toolchain making ramp up and usage of these features more complex than it has to be, and harder to troubleshoot, when it's something making production easier to maintain in the long run?
Because unless you suggest adding source maps to CSS (even though they still are not in JS), a preprocessor generating CSS makes CSS far more annoying to debug or play around with than native constants support would (and even with source maps, the usability of devtools style inspectors and editors would be significantly inferior to native support)
Re:What's new in CSS4
by alexchamberlain on Thursday October 27, 2011 @07:25AM
(#3162521)
I wouldn't mind a Chrome/Firefox extension to play around with extended CSS, but in production, I'm on the side of higher performance in Web Browser, which comes from simple style syntax.
> I'm on the side of higher performance in Web Browser, which comes from simple style syntax.
Constant parsing and replacement would add pretty much no overhead to CSS parsing in the grand scheme of things.