Live data from Hacker News

The State of CSS 2019

2019.stateofcss.com

31–40 of 68 posts

Re: The State of CSS 2019

#31
Unsurprisingly Stylus is one of the preprocessors that people want to avoid the most (beating less by 1% in user satisfaction). The preprocessor is very apathetic to what style you use - it's the antithesis of a linter. Want to use a semicolon on this line, and not one on the next? Go for it! Not the best when you want to write something production worthy.

That said I've found it phenomenal for prototyping, simple codepen examples, and teaching css. I run the prototyping efforts at Atlassian and I've built a large amount of code prototyping tools focused on allowing designers to quickly build something out. The standard template I give to designers and students uses stylus by default because it allows them to make mistakes. People who are unfamiliar with code feel defeated when a small syntax error was the one thing holding them back - it makes them question their understanding of the intention of what they wrote, even when the meaning of what they had was correct. Stylus fixes so many of these things for me. I'd highly recommend doing any of your exploratory phases in Stylus.

Re: The State of CSS 2019

#32
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/

> and it doesn't even fit on mobile

It loaded fine for me... Firefox Focus on OnePlus 6T

Re: The State of CSS 2019

#34

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.

CSS is a list of declarations. There is nothing esoteric about it.

You can read it from top to bottom and understand what the defined styles will look like when they are rendered.

If your naming is done correctly and your files are separated by features, there is no reason why you can't understand and visualize everything that is defined.

Re: The State of CSS 2019

#35
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/

I mean, even before getting to not responsive the choice of colours is annoying: two not so distant shades of blue, a joy to watch on mobile, especially with the blur shadow added to headers

Re: The State of CSS 2019

#36
> CSS on the other hand has always been the studious, well-behaved kid who always stays polite and never makes a rash decision

This is such a strange picture to paint!

CSS has always been the dim-witted kid. For a long time, it couldn't do math. For a long time, it couldn't have varibles. For a long time, it did not have a reasonable syntax for page layout. Its rules have global visibility (if we don't consider shadow DOM). And those vendor prefixes! This is one hell of a kid!

Re: The State of CSS 2019

#37
post #31

Unsurprisingly Stylus is one of the preprocessors that people want to avoid the most (beating less by 1% in user satisfaction). The preprocessor is very apathetic to what style you use - it's the antithesis of a linter. Want to use a semicolon on this line, and not one on the next? Go for it! Not the best when you want to write something production worthy. That said I've found it phenomenal for prototyping, simple co…

> Want to use a semicolon on this line, and not one on the next? Go for it! Not the best when you want to write something production worthy.

What do semicolons - or braces, for that matter - have to do with production worthiness? Style inconsistencies do not cause bugs. Poor CSS rules do.

Re: The State of CSS 2019

#38
post #6

Earlier quoted context omitted.

> 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.

You can definitely run Qt on various platforms. That's the whole point of Qt to begin with :)

The ability to have CSS in most browsers (a total of three of them as of 2019 since IE is switching to Chromium) is not really an excuse for the state of CSS.

Re: The State of CSS 2019

#39
post #29

I 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.

As someone who hasn't done CSS in a while, with a 4K monitor and the knowledge how old pixel-based desktop apps look on it (VERY small), what's wrong with inches?

From my own non-CSS based graphics experience, the only problem with layouts specified in absolute sizes is that small lines look really bad on standard (<100dpi) monitors if not aligned to the physical screen pixels. (Not saying that's not bad!)

Re: The State of CSS 2019

#40
post #29

I 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.

That's 19.2px.
Post reply on HN