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

The State of CSS 2019

2019.stateofcss.com

Post reply on HN
Print view View original

11–20 of 68 posts

Re: The State of CSS 2019

#11

Post by okbake »

Theodores wrote: post #5

The HTML in the report tells me as much about the state of CSS as what is in the report. Sure a lot of people know lots of clever CSS things, but are we over-complicating things and forgetting the basics of HTML? This report does not use HTML properly. It is a sea of divs which is all well and good for CSS but not what this whole thing is ultimately about. The document structure has a main element but this is in the…

It looks like a element is allowed to have div ancestors: https://html.spec.whatwg.org/multipage/grouping-content.html...

Re: The State of CSS 2019

#12

Post by Cogito »

If this was a photo pasted into word that was then printed and faxed it wouldn’t make the content any less meaningful.

Thanks for sharing the interesting results into various usages of css; I learnt about some new things, and found the usage of different things (especially units!) very interesting.

As an aside, the site worked great for me on mobile. Some images were big and slightly awkward to scroll around, but worked just fine.

Re: The State of CSS 2019

#15

Post by Sahhaese »

hornet-run wrote: post #9

There's a missing feature. Look at a css page and know how the site will behave. Every programing language you look at code (if well written) and u know what it will do. In css you know what are the attributes set but it doesn't really tell you what is going you happen. That's the only thing I don't like in css.

This is the killer reason why I hate doing anything with CSS. There's close to zero predictability.

CSS has no isolation / encapsulation, no control flow and no local state. Every line of code can modify and affect every other line. And even then, what happens is then dependent on an independently defined DOM object.

Yes, it's possible to write CSS in a way that helps ease the problems that the missing features above cause, but that's working harder to work around the language.

The raison d'etre of CSS, "style independently of the semantic document" is a failed project. It works for DOM trees that can be legitimately considered documents but fails horribly for what can be considered 'applications'. For that reason, I think an overhaul of web document styling is much needed.

The purists will cry that most of what is delivered on the web are "applications" and not "documents", especially when it comes to the morning news, but pretending that isn't the case isn't helpful.

Re: The State of CSS 2019

#16

Post by rimliu »

Sahhaese wrote: post #15
hornet-run wrote: post #9

There's a missing feature. Look at a css page and know how the site will behave. Every programing language you look at code (if well written) and u know what it will do. In css you know what are the attributes set but it doesn't really tell you what is going you happen. That's the only thing I don't like in css.

This is the killer reason why I hate doing anything with CSS. There's close to zero predictability. CSS has no isolation / encapsulation, no control flow and no local state. Every line of code can modify and affect every other line. And even then, what happens is then dependent on an independently defined DOM object. Yes, it's possible to write CSS in a way that helps ease the problems that the missing features above…

Maybe web tech for applications is the failed project, not the CSS.

Re: The State of CSS 2019

#17

Post by douglaswlance »

Theodores wrote: post #5

The HTML in the report tells me as much about the state of CSS as what is in the report. Sure a lot of people know lots of clever CSS things, but are we over-complicating things and forgetting the basics of HTML? This report does not use HTML properly. It is a sea of divs which is all well and good for CSS but not what this whole thing is ultimately about. The document structure has a main element but this is in the…

It was built with React, so they don't really care about how the actual HTML elements are laid out.

Re: The State of CSS 2019

#19

Post by rawTruthHurts »

hornet-run wrote: post #9

There's a missing feature. Look at a css page and know how the site will behave. Every programing language you look at code (if well written) and u know what it will do. In css you know what are the attributes set but it doesn't really tell you what is going you happen. That's the only thing I don't like in css.

> Every programing language you look at

Isn't the point of CSS that it's not a programming language? It's just a list of properties, after all.

Re: The State of CSS 2019

#20

Post by Theodores »

okbake wrote: post #11
Theodores wrote: post #5

The HTML in the report tells me as much about the state of CSS as what is in the report. Sure a lot of people know lots of clever CSS things, but are we over-complicating things and forgetting the basics of HTML? This report does not use HTML properly. It is a sea of divs which is all well and good for CSS but not what this whole thing is ultimately about. The document structure has a main element but this is in the…

It looks like a element is allowed to have div ancestors: https://html.spec.whatwg.org/multipage/grouping-content.html...

True, you can have as many divs as you want. But it can't be in a more sensible element and there is no good reason with today's CSS layout to want to put it in untold wrappers. Maybe it is a react thing where everything has to be in div wrappers.

Anyway, if the spec matters more than the toolchain it should not be anywhere but directly under the body element.

Post reply on HN