i[HN Gopher] Concrete.css null.host 1 i___________________________________________________________________ null.host 1 i null.host 1 iConcrete.css null.host 1 i null.host 1 iAuthor : soap- null.host 1 iScore : 300 points null.host 1 iDate : 2024-02-08 04:04 UTC (18 hours ago) null.host 1 i null.host 1 hweb link (concrete.style) URL:https://concrete.style hngopher.com 70 0w3m dump (concrete.style) /archive/2024/2024-02-08/items/39297949/dump.txt hngopher.com 70 i null.host 1 i| ambigious7777 wrote: null.host 1 i| water.css[0] and pico.css[1] are some of my favorite classless null.host 1 i| css libraries. null.host 1 i| null.host 1 i| There's a full list of them here: null.host 1 i| https://github.com/dbohdan/classless-css null.host 1 i| null.host 1 i| [0]: https://watercss.kognise.dev/ [1]: https://picocss.com/ null.host 1 i null.host 1 i | thunderbong wrote: null.host 1 i | I've tried a few of these 'classless CSS'. But I mostly end up null.host 1 i | with 'water.css'. It gives me the least amount of surprises. null.host 1 i null.host 1 i | jszymborski wrote: null.host 1 i | Water is great. null.host 1 i | null.host 1 i | Simple.css is another one I like. Also super simple to null.host 1 i | customize. null.host 1 i | null.host 1 i | https://simplecss.org/ null.host 1 i null.host 1 i | julianwachholz wrote: null.host 1 i | I love Pico and wanted to point out there's very active null.host 1 i | development for a soon to be released v2: null.host 1 i | https://v2.picocss.com/ null.host 1 i null.host 1 i | lagt_t wrote: null.host 1 i | Pico with bootstrap's grid system would be a dream. null.host 1 i null.host 1 i | sgdesign wrote: null.host 1 i | You don't need a grid system now that CSS Grid exists. null.host 1 i null.host 1 i | lagt_t wrote: null.host 1 i | The responsiveness of bootstrap's grid is something that null.host 1 i | css doesn't have. With a few classes I can make the same null.host 1 i | site for mobile and ultra wide screen. null.host 1 i null.host 1 i | bemusedthrow75 wrote: null.host 1 i | This is very helpful! null.host 1 i | null.host 1 i | I've been looking for a tiny classless CSS framework to go with null.host 1 i | petite-vue in a build-step-free app for a microcontroller null.host 1 i | project. null.host 1 i | null.host 1 i | water.css looks a good candidate already but there are some null.host 1 i | others to investigate there. null.host 1 i null.host 1 i | jamietanna wrote: null.host 1 i | Water looks nice, I've not used that before. null.host 1 i | null.host 1 i | I usually use https://classless.de because it supports theming, null.host 1 i | so I can add the bare minimum CSS to make it feel like a null.host 1 i | different site to another of my sites using it. null.host 1 i null.host 1 i | Zababa wrote: null.host 1 i | I love the bookmarklet from water.css, it allows you to turn null.host 1 i | lots of websites into something more readable. null.host 1 i null.host 1 i | thunderbong wrote: null.host 1 i | Oh! I want aware of that! Thanks, have to look into it null.host 1 i null.host 1 i | brnt wrote: null.host 1 i | Vote for mvp.css [0] here. null.host 1 i | null.host 1 i | [0] https://andybrewer.github.io/mvp/ null.host 1 i null.host 1 i | vitorsr wrote: null.host 1 i | Here is another such list: null.host 1 i | null.host 1 i | https://github.com/dohliam/dropin-minimal-css null.host 1 i null.host 1 i | Alifatisk wrote: null.host 1 i | I suggest checking out milligram.io, I enjoyed using it a lot! null.host 1 i null.host 1 i| KTibow wrote: null.host 1 i| Some stuff like the drop down arrow doesn't look right in dark null.host 1 i| mode, would likely be fixed with `color-scheme: dark` null.host 1 i null.host 1 i | louismerlin wrote: null.host 1 i | There is no drop-down arrow in light mode either, which does null.host 1 i | create an accessibility issue, I'll have to reflect on that. null.host 1 i | null.host 1 i | I created the style-sheet to be as minimalist as possible, but null.host 1 i | there is such a thing as too much minimalism. null.host 1 i null.host 1 i| kmoser wrote: null.host 1 i| Not sure I would make the "disabled" buttons stand out more null.host 1 i| brightly than a regular button. In fact I would swap the colors null.host 1 i| of those buttons, or maybe make the disabled button greyed out. null.host 1 i null.host 1 i | infotainment wrote: null.host 1 i | Agreed. One thing that a lot of people miss when attempting to null.host 1 i | comply with WCAG contrast guidelines is that disabled controls null.host 1 i | are _specifically_ exempt. null.host 1 i | null.host 1 i | With good reason, IMO -- too much contrast and it's not clear null.host 1 i | that an element _is_ disabled. null.host 1 i null.host 1 i | geraldwhen wrote: null.host 1 i | And yet younguns with good eyes and no color blindness will null.host 1 i | be able to read the text, and others won't. null.host 1 i | null.host 1 i | If you let a designer put grey on grey once, they'll do it null.host 1 i | 10,000,000 times. null.host 1 i null.host 1 i | louismerlin wrote: null.host 1 i | I limited myself to black and white when creating the style- null.host 1 i | sheet, but maybe I should indeed add some kind of indicator for null.host 1 i | the "disabled" button, such as hatchings. null.host 1 i | null.host 1 i | edit: hatchings make the inner text unreadable, I'll play null.host 1 i | around with opacity and dotted lines, thank you to the users null.host 1 i | who proposed them. null.host 1 i | null.host 1 i | edit 2: went with dashed lines and published a new version. It null.host 1 i | even shaves off a couple of bytes off the minimized version :D null.host 1 i null.host 1 i | topicseed wrote: null.host 1 i | Opacity maybe would help here. null.host 1 i null.host 1 i | yreg wrote: null.host 1 i | Could border-style dashed/dotted work? null.host 1 i null.host 1 i | PetitPrince wrote: null.host 1 i | Hatching seems an excellent idea. null.host 1 i null.host 1 i | krsdcbl wrote: null.host 1 i | this could be a rare but very practical usecase for strike- null.host 1 i | through text null.host 1 i null.host 1 i | yreg wrote: null.host 1 i | Wow, I love that! null.host 1 i null.host 1 i | kthartic wrote: null.host 1 i | Hmm I think the dashed lines still don't say to me "disabled" null.host 1 i | unless you told me. It looks more like a secondary button (eg null.host 1 i | "Go back" or "Cancel"). I really do think the use of reduced null.host 1 i | opacity would make sense here :) null.host 1 i null.host 1 i | sn0wleppard wrote: null.host 1 i | The buttons also need a hover/focus state, easy win for null.host 1 i | accessibility there null.host 1 i null.host 1 i | krsdcbl wrote: null.host 1 i | definitely - could use outline property, transforms/thickened null.host 1 i | borders or border radius animations if it's Imperative to null.host 1 i | keep things black and white null.host 1 i null.host 1 i | kmoser wrote: null.host 1 i | Agreed, maybe even just invert it to white-on-black on hover. null.host 1 i null.host 1 i| n3storm wrote: null.host 1 i| I am a big fan of brutalism but having all those line with same null.host 1 i| weight and hierarchy in terms of width, proximity and absolute null.host 1 i| black keeps me out from focusing in textual content. null.host 1 i null.host 1 i| jasonjmcghee wrote: null.host 1 i| Uptime sniper link is broken null.host 1 i null.host 1 i | sevg wrote: null.host 1 i | Looks like a failed/abandoned project. The user that opened the null.host 1 i | PR (only 6 months ago) to add uptimesniper to the list has null.host 1 i | since deleted their GitHub account, and the uptimesniper null.host 1 i | website and twitter are gone. I guess someone sniped its null.host 1 i | uptime! null.host 1 i null.host 1 i | louismerlin wrote: null.host 1 i | Yup, I'll remove it from the list, thank you for catching this. null.host 1 i null.host 1 i| robador wrote: null.host 1 i| This doesn't look right with the dark reader extension in null.host 1 i| firefox. I would expect a website that's compatible with dark null.host 1 i| mode to work with dark reader (I.e. I would expect dark reader to null.host 1 i| not influence the CSS in that case) null.host 1 i null.host 1 i | Semaphor wrote: null.host 1 i | That is sadly not the case. I disable dark reader for all sites null.host 1 i | supporting darkmode because it always changes them. null.host 1 i null.host 1 i | xigoi wrote: null.host 1 i | Are you using the dark mode detection feature? null.host 1 i null.host 1 i | Semaphor wrote: null.host 1 i | Oh wow, wanted to write "that does not exist", but finally null.host 1 i | found it unexpectedly under "configure website toggling". null.host 1 i | Thanks, that will remove a big annoyance if it works :D null.host 1 i null.host 1 i | julianwachholz wrote: null.host 1 i | I would never expect a browser extension to work flawlessly null.host 1 i | with every possible site out there. null.host 1 i | null.host 1 i | You are the user of the extension. Does it break a site? Submit null.host 1 i | a patch to the extension! Certainly don't complain to the null.host 1 i | website author who has no control over what extensions you null.host 1 i | personally use. null.host 1 i null.host 1 i| louismerlin wrote: null.host 1 i| Oh wow, crazy to see my project on HN! Thank you soap-3 for null.host 1 i| submitting it :D null.host 1 i| null.host 1 i| I really appreciate all of your suggestions, I'll patch the null.host 1 i| issues up asap. null.host 1 i null.host 1 i | asp_hornet wrote: null.host 1 i | It's really cool, what was some of your inspiration and null.host 1 i | thoughts behind it? null.host 1 i null.host 1 i | louismerlin wrote: null.host 1 i | I had been using similar projects such as skeleton[0] and null.host 1 i | milligram[1] for small experiments such as repfl[2], and null.host 1 i | wanted to create something similar that I would find null.host 1 i | aesthetically pleasing and that would fit in as little space null.host 1 i | as possible. The current version of concrete.css is less than null.host 1 i | 1kb minzipped! null.host 1 i | null.host 1 i | [0] http://getskeleton.com/ null.host 1 i | null.host 1 i | [1] https://milligram.io/ null.host 1 i | null.host 1 i | [2] https://repfl.ch/ null.host 1 i null.host 1 i | neitsab wrote: null.host 1 i | Please, please pretty please, can we stop with the automatic null.host 1 i | switching to dark mode if the system uses a dark theme? Chrome null.host 1 i | UI elements and webpages serve fundamentally different null.host 1 i | purposes, and have wildly different readability needs! null.host 1 i | null.host 1 i | At a minimum, please provide a way to switch between mode so null.host 1 i | that we can have some design granularity back. null.host 1 i | null.host 1 i | Thanks! null.host 1 i null.host 1 i | reitanuki wrote: null.host 1 i | I suspect this is a problem for your browser? The CSS media null.host 1 i | query only makes sense as 'prefers dark webpages' -- there'd null.host 1 i | be no point having it, if it means 'the browser theme is dark null.host 1 i | and it doesn't matter what the user prefers in terms of web null.host 1 i | pages'. null.host 1 i | null.host 1 i | Your browser should offer you a setting to choose whether you null.host 1 i | prefer dark webpages or not (SEPARATELY from the browser null.host 1 i | theme). Not sure if Chrome currently does but if this annoys null.host 1 i | you, it would be worth looking for. null.host 1 i null.host 1 i| numtel wrote: null.host 1 i| I used this for a few hackathon projects. It's great for simple null.host 1 i| layouts null.host 1 i| null.host 1 i| https://ethglobal.com/showcase/lwned-75x0f null.host 1 i| null.host 1 i| https://ethglobal.com/showcase/undefined-88xn6 null.host 1 i null.host 1 i| rcarmo wrote: null.host 1 i| Very nice. I do have to wonder what the Web would have been like null.host 1 i| if browser default style sheets were less crappy and actually null.host 1 i| thought out like this. null.host 1 i null.host 1 i | blowski wrote: null.host 1 i | About the same as it is. My time working in web agencies has null.host 1 i | taught me that the vast majority of website owners don't want null.host 1 i | to look the same as everyone else, and they want whizzbang null.host 1 i | high-tech widgets that make them look advanced. Usability all null.host 1 i | comes second to that. null.host 1 i null.host 1 i| theodorc wrote: null.host 1 i| Its fun and it looks good, but if you ever want to migrate away null.host 1 i| from it you pretty much have style everything all over? You can't null.host 1 i| just change the style of a a single tag? null.host 1 i null.host 1 i | louismerlin wrote: null.host 1 i | Alternatively you can migrate to another classless framework null.host 1 i | and not change a thing :) null.host 1 i | null.host 1 i | https://github.com/dbohdan/classless-css null.host 1 i null.host 1 i| notfed wrote: null.host 1 i| Would this be more correctly called a CSS "stylesheet"? null.host 1 i| null.host 1 i| Calling it a "CSS framework" really sent me in a loop trying to null.host 1 i| figure out what "framework" means. null.host 1 i null.host 1 i | geek_at wrote: null.host 1 i | Modern CSS stylesheets include configurability via CSS null.host 1 i | variables on the root element so maybe that's where the null.host 1 i | "framework" comes from. null.host 1 i | null.host 1 i | Also note: This project looks like an even more minimized null.host 1 i | version of PicoCSS [1] null.host 1 i | null.host 1 i | [1] https://picocss.com/ null.host 1 i null.host 1 i | lf-non wrote: null.host 1 i | Oh pico looks very nice - and something I am likely to null.host 1 i | actually use. concrete is a bit too minimal for me. null.host 1 i | null.host 1 i | I like the concept of classess css but most of the solutions null.host 1 i | I looked at (before pico) were just not very pleasing oob. null.host 1 i null.host 1 i | louismerlin wrote: null.host 1 i | Very good point, I modified the page. The project started-out null.host 1 i | non-classless, so the term was more appropriate back then. null.host 1 i null.host 1 i | bestest wrote: null.host 1 i | What you said is literally "Cascading Style Sheets stylesheet". null.host 1 i | Stick with "framework". null.host 1 i null.host 1 i | noduerme wrote: null.host 1 i | Why? Would you call a DVD disc a spaceship? null.host 1 i null.host 1 i | bestest wrote: null.host 1 i | Of course not. By I wouldn't say "DVD disc" because it's null.host 1 i | the same as "Digital Video Disc disc". null.host 1 i null.host 1 i | krsdcbl wrote: null.host 1 i | the somewhat lost term "boilerplate" comes to mind null.host 1 i null.host 1 i| tiborsaas wrote: null.host 1 i| Nice idea and naming, I love concrete and brutalism. null.host 1 i| null.host 1 i| I miss some concrete texture, could be easily done with SVG null.host 1 i| filters. Also, concrete is gray, but this is black and white, I'm null.host 1 i| not really sure that fits the theme perfectly. Maybe a single null.host 1 i| modifier class on the body would make sense. null.host 1 i| null.host 1 i| Edit: I see that it detects my OS dark theme, but the site could null.host 1 i| help me compare with the normal mode. null.host 1 i null.host 1 i | soap- wrote: null.host 1 i | You can change your preferred color scheme temporarily in dev null.host 1 i | tools null.host 1 i | null.host 1 i | I believe it's called concrete because of brutalist null.host 1 i | architecture and how it's almost always made with concrete null.host 1 i null.host 1 i| iraldir wrote: null.host 1 i| For personal projects, I really wish there was some sort of null.host 1 i| semantic CSS with many different implementations, which this null.host 1 i| could be one of them. null.host 1 i| null.host 1 i| What I mean is a set of rules on how to structure your HTML (like null.host 1 i| use a main element here) with some set expectations of how it null.host 1 i| will be structured on the page. null.host 1 i| null.host 1 i| Then, many different people could write different spritesheet null.host 1 i| that makes the same HTML looks widely different. I'm not just null.host 1 i| talking colour, but fonts, radius, opacity, animations, etc. etc. null.host 1 i| null.host 1 i| One stylesheet could make the HTML look barebone black and white, null.host 1 i| where another makes it look all in gradients of purple with fancy null.host 1 i| animations etc. null.host 1 i| null.host 1 i| All for the purpose of writing simple application where you don't null.host 1 i| care so much about how they look. null.host 1 i| null.host 1 i| - classes would not be used - CSS variables would not be used - null.host 1 i| just plain old div, H1, section etc. null.host 1 i null.host 1 i | FireInsight wrote: null.host 1 i | Semantic HTML exists and is usable, most developers just want null.host 1 i | to make their site look like _they_ want (nothing wrong with null.host 1 i | that). Problems arise when sites don 't use semantic elements, null.host 1 i | style with bespoke class systems. And functionality or markup null.host 1 i | can't be changed with CSS, so when that's related to the theme null.host 1 i | it's quite hard to change. null.host 1 i null.host 1 i| Tade0 wrote: null.host 1 i| 1. Modify the base font-size to 62.5% so that 1.6rem = 16px. null.host 1 i| null.host 1 i| That is not a given as it depends on browser settings and it null.host 1 i| generally doesn't mix well with other CSS that might not make the null.host 1 i| same assumption. null.host 1 i null.host 1 i | louismerlin wrote: null.host 1 i | I borrowed this from Milligram[0] because it seemed like a sane null.host 1 i | thing to do at the time. Would your recommendation be to not null.host 1 i | anything to the base font-size and adjust the REM sizes null.host 1 i | accordingly? null.host 1 i | null.host 1 i | [0] null.host 1 i | https://github.com/milligram/milligram/blob/d895f179623b56f3... null.host 1 i null.host 1 i | Tade0 wrote: null.host 1 i | Yes. null.host 1 i | null.host 1 i | In relation to this since you're using rem for borders and null.host 1 i | progress bar height, it's all going to scale along with null.host 1 i | browser-defined font size. You might not want that, as people null.host 1 i | typically increase this setting to have just the text larger. null.host 1 i null.host 1 i| asp_hornet wrote: null.host 1 i| I love it. Simple and restrained with kind of a retro macintosh null.host 1 i| feel. null.host 1 i null.host 1 i| vvoyer wrote: null.host 1 i| Simple, to the point, love it null.host 1 i null.host 1 i| jug wrote: null.host 1 i| Refreshingly simple, almost to the point of an aversion to other null.host 1 i| minimalist competitors like Milligram. null.host 1 i| null.host 1 i| I like it. As someone else said here, it brings my mind to an null.host 1 i| alternative web with browsers that had a better default and null.host 1 i| standardized stylesheet. Oh how I wish for this. Can't just null.host 1 i| Chrome, Firefox, Edge, Safari all just adopt this one? null.host 1 i| null.host 1 i| Setting up no-CSS sites would be a more sensible thing and we null.host 1 i| would have less need of Gemini (https://geminiprotocol.net/). null.host 1 i| null.host 1 i| One can dream... Of course, now sites widely rely on a random set null.host 1 i| of margin defaults, base sizes etc. brought into their websites, null.host 1 i| so ripping out and changing those wouldn't be quite that simple. null.host 1 i null.host 1 i | yoavm wrote: null.host 1 i | To be fair, to create a web that has no need for Gemini I think null.host 1 i | no-JS sites would take us much further than no-CSS. It's null.host 1 i | relatively easy to disable CSS (Firefox: View - Page style - No null.host 1 i | style), and generally not much will actually break. But null.host 1 i | disabling JS would more than often break the website null.host 1 i | functionality completely. null.host 1 i null.host 1 i | chiefalchemist wrote: null.host 1 i | re: Project Gemini - Gemini in 100 words null.host 1 i | null.host 1 i | Reading that reminds us how far we have *not* come. We were null.host 1 i | promised jetpacks, and instead we got the internet. A pro- null.host 1 i | distraction, privacy violating, social fabric tearing, power null.host 1 i | tool. null.host 1 i | null.host 1 i | More Big Brother, less prophet / savior. null.host 1 i null.host 1 i | AeroNotix wrote: null.host 1 i | My honest hot take is that we made computers too easy to use. null.host 1 i | null.host 1 i | I appreciate how liberating computers and the internet can be null.host 1 i | for a lot of people but it has been far too easy to implement null.host 1 i | dark control through them. null.host 1 i null.host 1 i | _benj wrote: null.host 1 i | If I dare reply your hot take with my hot take, It was null.host 1 i | engineers who implemented those dark patterns. I think that null.host 1 i | still "lots of people" see excel formulas as stuff that null.host 1 i | geniuses do, so I think it comes down to us. Will I write null.host 1 i | that privacy invading, psychologically manipulating code, null.host 1 i | or would I say no. null.host 1 i | null.host 1 i | Sure, if I don't do it "somebody else would", but I wonder null.host 1 i | if that mentality has taken us here null.host 1 i null.host 1 i| andriamanitra wrote: null.host 1 i| It looks great but I would not be able to use it as-is because null.host 1 i| different kinds of elements (button, textbox, dropdown) look too null.host 1 i| similar. I'd rather make an ugly but usable site than the other null.host 1 i| way around. null.host 1 i null.host 1 i| self_awareness wrote: null.host 1 i| I'm really not a fan of brutalism (in UI and in architecture) and null.host 1 i| I think that our monitors have 24-bit color depth for a reason. null.host 1 i| Such extreme simplification of UI is not the way I think. null.host 1 i| null.host 1 i| (Microsoft has attempted this in Metro, but quickly withdrew from null.host 1 i| this idea) null.host 1 i null.host 1 i | WorldMaker wrote: null.host 1 i | Microsoft's Windows 8 era "Metro" guidelines were extremely null.host 1 i | colorful. They often emphasized one single brand accent as a null.host 1 i | standard across an app, but it could be just about any color null.host 1 i | you wanted. Or one single accent color of the user's choice to null.host 1 i | give them a sense of personal ownership. They also emphasized null.host 1 i | the importance of "full bleed" photography and what a colorful null.host 1 i | wallpaper with basic parallax effects can do to make an app null.host 1 i | seem alive. null.host 1 i | null.host 1 i | Most of the really vibrant "magazines" and apps and "hubs" only null.host 1 i | ever really existed on Windows Phones at that time and most null.host 1 i | desktop apps stuck to a bare minimum so most people missed all null.host 1 i | the good colorfully and playfully vibrant examples of what null.host 1 i | those UI guidelines could be when done right. null.host 1 i null.host 1 i| maxk42 wrote: null.host 1 i| I've been loving classless CSS frameworks and have been using null.host 1 i| them extensively for personal projects for around four years now. null.host 1 i null.host 1 i| cyco130 wrote: null.host 1 i| Looks fine to me apart from the buttons. But if we're talking null.host 1 i| about "classless", some _has_ to mention Marx[1]. null.host 1 i| null.host 1 i| [1] https://mblode.github.io/marx null.host 1 i null.host 1 i| poidos wrote: null.host 1 i| See neat.css [0] for another take on this. null.host 1 i| null.host 1 i| [0]: https://neat.joeldare.com/ null.host 1 i null.host 1 i| nc0 wrote: null.host 1 i| As it is often said in various designer forums, please avoid pure null.host 1 i| white (#FFFFFF) on black (here #111111), as it makes the text null.host 1 i| glow for the human eyes (therefore making it unreadable for long null.host 1 i| text). Instead, try to lower a bit the contrast on the text null.host 1 i| color. null.host 1 i| null.host 1 i| Also, the dispositions for the buttons at the beginning (GitHub, null.host 1 i| NPM, ...) are not adjusted correctly for keyboard navigation null.host 1 i| (each button requires two tabs). null.host 1 i| null.host 1 i| Appart from that, I do like a minimalist stylesheet, so I will null.host 1 i| also recommend Tufte CSS [0] for readers. null.host 1 i| null.host 1 i| [0]: https://github.com/edwardtufte/tufte-css null.host 1 i null.host 1 i | dvdkon wrote: null.host 1 i | This really depends on the user's display and the viewing null.host 1 i | conditions. Someone with a TN LCD or even an OLED in bright null.host 1 i | light would likely prefer the "high contrast" #FFF on #000. null.host 1 i null.host 1 i | pier25 wrote: null.host 1 i | It's also an accessibility issue. People with astigmatism null.host 1 i | might have a hard time with bright text over dark background. null.host 1 i | null.host 1 i | https://medium.com/@h_locke/why-dark-mode-causes-more- null.host 1 i | access... null.host 1 i null.host 1 i | codingcoyote wrote: null.host 1 i | As someone with astigmatism, I prefer dark modes in almost null.host 1 i | all places as long as it's done correctly. Bright screens null.host 1 i | with dark text cause significantly more eyestrain for me. null.host 1 i | My wife also has astigmatism and prefers light backgrounds null.host 1 i | with dark text. For the same reasons. I think the key here null.host 1 i | for accessibility is choice. null.host 1 i null.host 1 i | pier25 wrote: null.host 1 i | I agree, users should be able to pick whatever works null.host 1 i | better for them. null.host 1 i | null.host 1 i | There's a myth going on that dark mode is null.host 1 i | universally/objectively better which is simply false. null.host 1 i null.host 1 i | Swizec wrote: null.host 1 i | I too have astigmatism and am a light mode enjoyer. Dark null.host 1 i | mode makes the letters dance in front of my eyes. null.host 1 i | null.host 1 i | Display brightness at 20% is life. Never made sense to me null.host 1 i | why you'd shine the light of a thousand suns in your eyes null.host 1 i | then put sunglasses on it because "it's too bright" when null.host 1 i | you could just not. null.host 1 i | null.host 1 i | My partner is a dark mode user and honestly sometimes her null.host 1 i | phone screen lights up the whole bedroom. Even with dark null.host 1 i | mode. I don't understand. null.host 1 i null.host 1 i | antisthenes wrote: null.host 1 i | I'm with your wife on this one, and also either one of null.host 1 i | those is way better than "grey on whatever" that seemed null.host 1 i | to be a prevalent design choice for a few years for many null.host 1 i | websites. null.host 1 i | null.host 1 i | Low contrast is hell. null.host 1 i null.host 1 i | lelandbatey wrote: null.host 1 i | Environmental lighting conditions rule the day! I have null.host 1 i | astigmatism and I prefer bright backgrounds; #000 text on null.host 1 i | #fff backgrounds works great for me, but that's because I null.host 1 i | work in a room lit by a 250W 30,000 lumen corn-cob LED null.host 1 i | bulb[0] that makes my small office as bright on the null.host 1 i | inside as the shaded ground from a tree on an overcast null.host 1 i | day (which is quite bright compared to usual indoor null.host 1 i | lighting). In a room that bright, high contrast text null.host 1 i | works great and is highly readable, with "dark mode" null.host 1 i | often looking washed out and muddy. Even small reductions null.host 1 i | in contrast (such as what https://devdocs.io does with null.host 1 i | text of #333 in light mode) can make me notice and wish null.host 1 i | for greater contrast. null.host 1 i | null.host 1 i | [0] - https://www.benkuhn.net/lux/ null.host 1 i null.host 1 i | treflop wrote: null.host 1 i | I have astigmatism and dark mode is hard to read. null.host 1 i | null.host 1 i | Black text on white background all day. null.host 1 i null.host 1 i | lancesells wrote: null.host 1 i | Tufte is really nice but requires a custom font, which IMO is null.host 1 i | no longer minimal. null.host 1 i | null.host 1 i | And totally agree with black text on white. null.host 1 i null.host 1 i | nc0 wrote: null.host 1 i | Agree, that depends on your vision of minimalism and stuff. null.host 1 i null.host 1 i | seanwilson wrote: null.host 1 i | > As it is often said in various designer forums, please avoid null.host 1 i | pure white (#FFFFFF) on black (here #111111), as it makes the null.host 1 i | text glow for the human eyes (therefore making it unreadable null.host 1 i | for long text). Instead, try to lower a bit the contrast on the null.host 1 i | text color. null.host 1 i | null.host 1 i | If you want an objective measure for this, see APCA: null.host 1 i | https://www.myndex.com/APCA/?BG=000000&TXT=ffffff&DEV=G4g&BU... null.host 1 i | null.host 1 i | From https://git.apcacontrast.com/documentation/APCA_in_a_Nutsh null.host 1 i | el...: "Lc 90 is a suggested maximum for very large and bold null.host 1 i | fonts (greater than 36px bold), and large areas of color". null.host 1 i | White on black scores Lc 108. null.host 1 i | null.host 1 i | It's the likely future replacement for the standard WCAG2 null.host 1 i | contrast checker (which becomes really inaccurate for dark mode null.host 1 i | and I don't think makes any suggestion about maximum contrast). null.host 1 i null.host 1 i| kkarpkkarp wrote: null.host 1 i|