Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: CSS Extras

github.com

Post reply on HN
Print view View original

1–10 of 66 posts

Re: Show HN: CSS Extras

#2

Post by christophilus »

Whoo. I’ll be the first hyper negative prototypical HN commenter.

I’m glad I don’t work on browser engines for a living. CSS is getting more complex and spaghetti-capable by the day.

> Currently only supported in Chrome 141+. The @function rule is going through the W3C standardization process and will be available in other browsers soon.

Also, pretty tired of Chrome effectively front-running standards as a not-so-subtle means of cramming them through.

Re: Show HN: CSS Extras

#3

Post by cluckindan »

Welp, time to make a @function preprocessor. There is no reason for every single client to recalculate things which could have been completely or partially calculated at build time.

Re: Show HN: CSS Extras

#4

Post by Hendrikto »

christophilus wrote: post #2

Whoo. I’ll be the first hyper negative prototypical HN commenter. I’m glad I don’t work on browser engines for a living. CSS is getting more complex and spaghetti-capable by the day. > Currently only supported in Chrome 141+. The @function rule is going through the W3C standardization process and will be available in other browsers soon. Also, pretty tired of Chrome effectively front-running standards as a not-so-sub…

Web standards are in the same boat as C++. They can never really deprecate anything, but they want shiny new things, so they just add and add on top of the pile.

Every feature sounds great in isolation, but in aggregate they become a moloch.

Then people say “modern CSS is great, you just have to pick the ‘good subset’.”, but then nobody can agree what that subset should be, and everybody else uses a different subset.

LLMs also contribute to this, as 90% of what’s available on the web is considered outdated now, but that is the majority of training data.

Re: Show HN: CSS Extras

#5

Post by runroader »

christophilus wrote: post #2

Whoo. I’ll be the first hyper negative prototypical HN commenter. I’m glad I don’t work on browser engines for a living. CSS is getting more complex and spaghetti-capable by the day. > Currently only supported in Chrome 141+. The @function rule is going through the W3C standardization process and will be available in other browsers soon. Also, pretty tired of Chrome effectively front-running standards as a not-so-sub…

One person's front-running is another's reference implementation.

Although, yes, CSS is getting more complex because everything on the web is. What's the last standard feature to really be taken away after actually existing in the wild for a while? XHTML and Flash (effectively a standard if not in reality)?

Re: Show HN: CSS Extras

#6

Post by bastawhiz »

christophilus wrote: post #2

Whoo. I’ll be the first hyper negative prototypical HN commenter. I’m glad I don’t work on browser engines for a living. CSS is getting more complex and spaghetti-capable by the day. > Currently only supported in Chrome 141+. The @function rule is going through the W3C standardization process and will be available in other browsers soon. Also, pretty tired of Chrome effectively front-running standards as a not-so-sub…

The standard for this has been developed in the open at the CSSWG with one of the SASS developers:

https://github.com/w3c/csswg-drafts/issues/9350

Re: Show HN: CSS Extras

#8

Post by gregoriol »

cluckindan wrote: post #3

Welp, time to make a @function preprocessor. There is no reason for every single client to recalculate things which could have been completely or partially calculated at build time.

CSS is becoming a programming language and not just a style sheet. Don't worry about performance, soon you'll be able to run assembly in it.

Re: Show HN: CSS Extras

#9

Post by mark_and_sweep »

runroader wrote: post #5
christophilus wrote: post #2

Whoo. I’ll be the first hyper negative prototypical HN commenter. I’m glad I don’t work on browser engines for a living. CSS is getting more complex and spaghetti-capable by the day. > Currently only supported in Chrome 141+. The @function rule is going through the W3C standardization process and will be available in other browsers soon. Also, pretty tired of Chrome effectively front-running standards as a not-so-sub…

One person's front-running is another's reference implementation. Although, yes, CSS is getting more complex because everything on the web is. What's the last standard feature to really be taken away after actually existing in the wild for a while? XHTML and Flash (effectively a standard if not in reality)?

XHTML (or the XML syntax for HTML) wasn't removed (see: https://html.spec.whatwg.org/multipage/introduction.html#htm...). You may be thinking of XSLT, which may be removed in future.
Post reply on HN