Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I like the part where people get so attached to a tool that they've learned that they reject change. Like your message. Comparing a preprocessor to a native element is asinine. Do you argue against JavaScript features because, given that it's a turing complete language, such things could simply be done with preprocessors?

Seriously the boorish comments about "no support yet" are like listening to fat client advocates in the 90s.



It's not so much about attachment to current tools. It's just that you look at something like this, with all its cumbersome syntax, and wonder why they had to make it so ridiculous. And it's not like nobody had any decent ideas of how to do a nice, simple, clean syntax for variables. In the end I suppose we'll be able to continue using preprocessors, and maybe they can generate the clumsy native CSS variables, so it won't really matter and we'll get the best of both worlds. But it sure would be nice if they wouldn't create new features that instantly feel cumbersome to use compared to what people have already been using.


Agreed, we are embedding chromium in our desktop apps. Here we can depend fully on the features this particular browser version supports.

Cross browser support is not always necessary.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: