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

61–68 of 68 posts

Re: The State of CSS 2019

#61

Post by __oh_es »

seanwilson wrote: post #59
jjcm wrote: post #46

Earlier quoted context omitted.

Inconsistencies in the source file do not affect production worthiness in the moment, but they do affect maintainability down the line. If for instance your team wants to move to a new css preprocessor that's the next big thing in 10 years, a consistent style means you can programatically convert to the new syntax. Or maybe there's a tool that can help you write better css and detect where rules are unused -variable…

Clear and consistent code formatting guidelines (and ideally automatic formatting for this) is also great for reducing the thought required in formatting code you push while reducing noise and code formatting debates in code reviews.

Can’t second this enough

Re: The State of CSS 2019

#62

Post by celticmusic »

azangru wrote: post #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 shado…

remember when CSS couldn't center horizontally in a reasonable way? Pepperidge Farm remembers.

Re: The State of CSS 2019

#63

Post by Nicksil »

jjcm wrote: 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.

It's likely being used for _print_ css.

Re: The State of CSS 2019

#64

Post by sureaboutthis »

actionscripted wrote: post #57
sureaboutthis wrote: post #48

Earlier quoted context omitted.

For a long time, it didn't need any of those things. It's only been a recent need for marketing, mainly.

Not even close. Marketing has lead to some absurd uses of CSS but it's more about adaptive/responsive design. When you need to handle an almost unlimited range of screen sizes having your visual system able to handle a little math is critical.

First there was marketing. Then there was adaptive design. And variables are new compared to almost everything else.

Re: The State of CSS 2019

#65

Post by Bluestrike2 »

sureaboutthis wrote: post #64
actionscripted wrote: post #57

Earlier quoted context omitted.

Not even close. Marketing has lead to some absurd uses of CSS but it's more about adaptive/responsive design. When you need to handle an almost unlimited range of screen sizes having your visual system able to handle a little math is critical.

First there was marketing. Then there was adaptive design. And variables are new compared to almost everything else.

There's a CSS & FP Working Group note that listed variables--or more specifically, symbolic constants--as a proposed future extension to CSS2 back in 1998,[0] and I'd assume that there are even earlier discussions on the matter as well. The idea of using variables in CSS isn't new by any means. If you read this 2008 essay by Bert Bos[1] against extending CSS to include variables Bos makes a really intriguing comment that "macros help for authors, not for the semantic Web" in his conclusion.

Perhaps I'm reading into things, but it seems rather illuminative in terms of understanding how at least some key figures in the development of CSS may have viewed things. If you consider CSS in terms of two distinct audiences--authors/maintainers and users who consume CSS-styled documents--then at least some of the decisions with the CSS specifications seem to make a bit more sense. In which case, it's not so much that CSS didn't need the listed functionality as it is that other goals for the specifications were prioritized over the benefits of variables and other functionality. Reusability, modularity, and simplicity were some of the main priorities. They still are, but I think we've seen a redefinition of those terms with the direction front-end development has taken in the past decade; I also think that improvements in the uniformization of browser implementations and development of better debugging tools has helped erase some of the concerns given in the essay.

0. https://www.w3.org/TR/NOTE-CSS-potential#id05684046681

1. https://www.w3.org/People/Bos/CSS-variables

Re: The State of CSS 2019

#66

Post by txtsd »

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/

Works fine in Mozilla's Reference Browser on Honor 7X.

Re: The State of CSS 2019

#67

Post by sureaboutthis »

Bluestrike2 wrote: post #65
sureaboutthis wrote: post #64

Earlier quoted context omitted.

First there was marketing. Then there was adaptive design. And variables are new compared to almost everything else.

There's a CSS & FP Working Group note that listed variables--or more specifically, symbolic constants--as a proposed future extension to CSS2 back in 1998,[0] and I'd assume that there are even earlier discussions on the matter as well. The idea of using variables in CSS isn't new by any means. If you read this 2008 essay by Bert Bos[1] against extending CSS to include variables Bos makes a really intriguing comment…

> other goals for the specifications were prioritized over the benefits of variables and other functionality.

That's what I said. Until marketing forces clamored for such things, other less interesting things that weren't sparkles and lollipops took precedence.

Re: The State of CSS 2019

#68

Post by hkai »

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…

Many people heard your pain so this is why in Vue.js CSS is isolated, while in react you can use styled components for encapsulation, sort of.
Post reply on HN