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

1–10 of 68 posts

Re: The State of CSS 2019

#3

Post by blowski »

dmitriid wrote: post #2

Kinda all you need to know about the state of CSS in 2019: the menu’s bottom items cannot be accessed on mobile Safari. Also: the scrolling is awkward/broken.

If half the effort put into shitting on CSS went instead to improving it, maybe it would be perfect by now. The requirements of CSS as a language are insanely complicated - open source, implemented by different browsers, on all different devices, for applications doing a huge variety of things, working with 20 years of legacy code. I defy anyone to explain how they would do it better and still satisfy all the constraints.

Re: The State of CSS 2019

#5

Post by Theodores »

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 wrong place. According to the HTML spec the main element should be directly below the body element with no extra div wrappers.

Then the page has one nav element. Beyond that it uses none of the sensible HTML5 elements for the content. Nothing is broken down into sections, articles and asides. Graphs are not in figures.

These elements are important, otherwise we might as well just give up and just post images with imagemaps.

Surely some content on the report must be a 'header' or part of what you might call a 'footer'?

I don't get this complacency when it comes to writing HTML, why everything always has to be in a div when the spec says you should only being divs when there are no better elements.

Since this report is entirely written in div soup with one nav element and one badly placed main, they don't know HTML so why should I take seriously what the report says about CSS? It is going to be the same cargo cult stuff.

Re: The State of CSS 2019

#6

Post by dmitriid »

blowski wrote: post #3
dmitriid wrote: post #2

Kinda all you need to know about the state of CSS in 2019: the menu’s bottom items cannot be accessed on mobile Safari. Also: the scrolling is awkward/broken.

If half the effort put into shitting on CSS went instead to improving it, maybe it would be perfect by now. The requirements of CSS as a language are insanely complicated - open source, implemented by different browsers, on all different devices, for applications doing a huge variety of things, working with 20 years of legacy code. I defy anyone to explain how they would do it better and still satisfy all the constra…

> If half the effort put into shitting on CSS went instead to improving it, maybe it would be perfect by now.

More than half of effort is put into improving it. Too little reaches the final stages.

> I defy anyone to explain how they would do it better and still satisfy all the constraints.

I had a rant or two about this in the past: https://medium.com/@dmitriid/ok-w3c-and-whatwg-dont-die-but-... :)

CSS and HTML still pretend they are just text and images on a paper (or a 2D plane). And this hasn't been the case for over 10 years. As a layout engine CSS still has less capabilities than Delphi or Qt from early 2000.

Re: The State of CSS 2019

#7

Post by usrme »

Liquidor wrote: post #4

I just can't take this website serious. Is it a parody or a joke? It looks awful and it doesn't even fit on mobile ( https://i.imgur.com/6GD8yfD.png && https://i.imgur.com/lxs0gVG.png ) What happened to keeping it simple? http://motherfuckingwebsite.com/ or http://bettermotherfuckingwebsite.com/

Won't comment about whether it looks awful or not, but in terms of the mobile experience it seems to work fine for me on my OnePlus 6T with Firefox Focus, and subsequent tests on desktop using the Responsive Design Mode in Firefox with various size also worked as expected.

Re: The State of CSS 2019

#9

Post by hornet-run »

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.
Post reply on HN