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

Concrete.css

concrete.style

Post reply on HN
Print view View original

81–90 of 117 posts

Re: Concrete.css

#81

Post by YuukiRey »

I skimmed the CSS and I don't see the appeal. There's no reason, in my opinion, to give a section a default `4rem` vertical padding. Given that the stylesheet is really small, I'd at best consider this a solution for a tiny proof of concept if you want to demonstrate something to colleagues. I'd rather suggest people copy it into their own CSS and use it as a template.

It also adds a margin to certain elements which is almost always a no-go. It's super rare that the margin around an element is part of this element's intrinsic properties.

In general I think people would get much more mileage out of https://every-layout.dev/ (not affiliated). It's one of the best programming related books I've read in a while and it really changed the way I think about CSS in general.

Re: Concrete.css

#82

Post by soap- »

tiborsaas wrote: post #33

Nice idea and naming, I love concrete and brutalism. I miss some concrete texture, could be easily done with SVG filters. Also, concrete is gray, but this is black and white, I'm not really sure that fits the theme perfectly. Maybe a single modifier class on the body would make sense. Edit: I see that it detects my OS dark theme, but the site could help me compare with the normal mode.

You can change your preferred color scheme temporarily in dev tools

I believe it's called concrete because of brutalist architecture and how it's almost always made with concrete

Re: Concrete.css

#83

Post by louismerlin »

YuukiRey wrote: post #81

I skimmed the CSS and I don't see the appeal. There's no reason, in my opinion, to give a section a default `4rem` vertical padding. Given that the stylesheet is really small, I'd at best consider this a solution for a tiny proof of concept if you want to demonstrate something to colleagues. I'd rather suggest people copy it into their own CSS and use it as a template. It also adds a margin to certain elements which…

Thank you for your comments, I've opened an issue and will look into best practice :)

https://github.com/louismerlin/concrete.css/issues/4

Re: Concrete.css

#84

Post by codingcoyote »

pier25 wrote: post #79
dvdkon wrote: post #66

Earlier quoted context omitted.

This really depends on the user's display and the viewing conditions. Someone with a TN LCD or even an OLED in bright light would likely prefer the "high contrast" #FFF on #000.

It's also an accessibility issue. People with astigmatism might have a hard time with bright text over dark background. https://medium.com/@h_locke/why-dark-mode-causes-more-access...

As someone with astigmatism, I prefer dark modes in almost all places as long as it's done correctly. Bright screens with dark text cause significantly more eyestrain for me. My wife also has astigmatism and prefers light backgrounds with dark text. For the same reasons. I think the key here for accessibility is choice.

Re: Concrete.css

#85

Post by WorldMaker »

self_awareness wrote: post #53

I'm really not a fan of brutalism (in UI and in architecture) and I think that our monitors have 24-bit color depth for a reason. Such extreme simplification of UI is not the way I think. (Microsoft has attempted this in Metro, but quickly withdrew from this idea)

Microsoft's Windows 8 era "Metro" guidelines were extremely colorful. They often emphasized one single brand accent as a standard across an app, but it could be just about any color you wanted. Or one single accent color of the user's choice to give them a sense of personal ownership. They also emphasized the importance of "full bleed" photography and what a colorful wallpaper with basic parallax effects can do to make an app seem alive.

Most of the really vibrant "magazines" and apps and "hubs" only ever really existed on Windows Phones at that time and most desktop apps stuck to a bare minimum so most people missed all the good colorfully and playfully vibrant examples of what those UI guidelines could be when done right.

Re: Concrete.css

#86

Post by pier25 »

codingcoyote wrote: post #84
pier25 wrote: post #79

Earlier quoted context omitted.

It's also an accessibility issue. People with astigmatism might have a hard time with bright text over dark background. https://medium.com/@h_locke/why-dark-mode-causes-more-access...

As someone with astigmatism, I prefer dark modes in almost all places as long as it's done correctly. Bright screens with dark text cause significantly more eyestrain for me. My wife also has astigmatism and prefers light backgrounds with dark text. For the same reasons. I think the key here for accessibility is choice.

I agree, users should be able to pick whatever works better for them.

There's a myth going on that dark mode is universally/objectively better which is simply false.

Re: Concrete.css

#87

Post by Swizec »

codingcoyote wrote: post #84
pier25 wrote: post #79

Earlier quoted context omitted.

It's also an accessibility issue. People with astigmatism might have a hard time with bright text over dark background. https://medium.com/@h_locke/why-dark-mode-causes-more-access...

As someone with astigmatism, I prefer dark modes in almost all places as long as it's done correctly. Bright screens with dark text cause significantly more eyestrain for me. My wife also has astigmatism and prefers light backgrounds with dark text. For the same reasons. I think the key here for accessibility is choice.

I too have astigmatism and am a light mode enjoyer. Dark mode makes the letters dance in front of my eyes.

Display brightness at 20% is life. Never made sense to me why you’d shine the light of a thousand suns in your eyes then put sunglasses on it because “it’s too bright” when you could just not.

My partner is a dark mode user and honestly sometimes her phone screen lights up the whole bedroom. Even with dark mode. I don’t understand.

Re: Concrete.css

#88

Post by antisthenes »

codingcoyote wrote: post #84
pier25 wrote: post #79

Earlier quoted context omitted.

It's also an accessibility issue. People with astigmatism might have a hard time with bright text over dark background. https://medium.com/@h_locke/why-dark-mode-causes-more-access...

As someone with astigmatism, I prefer dark modes in almost all places as long as it's done correctly. Bright screens with dark text cause significantly more eyestrain for me. My wife also has astigmatism and prefers light backgrounds with dark text. For the same reasons. I think the key here for accessibility is choice.

I'm with your wife on this one, and also either one of those is way better than "grey on whatever" that seemed to be a prevalent design choice for a few years for many websites.

Low contrast is hell.

Post reply on HN