Well.. as a developer who probably works more with CSS and HTML than anything else, I really enjoyed this report. I found the visualizations and even the overall design provocative, and I even learned a few things in the process (overscroll-behavior?!)
The State of CSS 2019
21–30 of 68 posts
Re: The State of CSS 2019
#22The 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.
That's no excuse. React has no opinions about which elements nest within which others. Since React 16, it doesn't even force unnecessary wrapper elements thanks to the inclusion of `React.fragment`.
Re: The State of CSS 2019
#23There'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…
> It works for DOM trees that can be legitimately considered documents
That's because this is what the web was built for. But then everyone wanted to turn it into an application platform by building on top of a document model. Of course CSS was designed to style documents.
Re: The State of CSS 2019
#24Earlier quoted context omitted.
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.
The comment you replied to points out that "main" can be inside a div according to the spec.
Also, React doesn't require the wrappers.
Re: The State of CSS 2019
#25Earlier quoted context omitted.
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 stil…
And you can't run Delphi or QT based projects on Windows, macOS, Linux and Haiku, in most of the browsers that run on all those operating systems.
Re: The State of CSS 2019
#26I 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/
It looks pretty perfect on mobile for me on Safari on iOS
Re: The State of CSS 2019
#27Re: The State of CSS 2019
#28There'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.
What layout system/language would work in a readable manner? To me layout is basically a way to express a set of constraints which can be sometimes contradictory. In CSS a problem rises because the system will always manage to resolve them, somehow, and there are no warnings. LaTeX or AutoLayout will help you write an unambiguous layout, but they are still inscrutable at a glance.
Re: The State of CSS 2019
#29I think the most offensive thing here is that 6.2% of people use inches as a unit of measure in their css.
The thought of 𝚋𝚘𝚛𝚍𝚎𝚛: 𝟶.𝟸𝚒𝚗 𝚋𝚕𝚊𝚌𝚔; sitting in someone's css is terrifying.
Re: The State of CSS 2019
#30I think the most offensive thing here is that 6.2% of people use inches as a unit of measure in their css. The thought of 𝚋𝚘𝚛𝚍𝚎𝚛: 𝟶.𝟸𝚒𝚗 𝚋𝚕𝚊𝚌𝚔; sitting in someone's css is terrifying.
I've used inches when doing print-based CSS, although I'd be surprised if that accounts for all of it.