upvote
Absolutely, this is accessibility 101.

The one counter argument to this that I would accept is that users don't know about font settings. But the proper solution if for browsers to make it easier those settings rather than every single website having to add font controls.

reply
While everyone probably should learn something about their devices, the defaults you provide to users should be good ones.

Drawing a line can be hard, but clearly the basic font should be contrast-y enough so that most people can read it, no? The user can control the defaults of many things on their devices, but we shouldn't require them to change settings to have a good experience. We already customize websites a lot.

I think it depends on the goals of the print version, but people spend a lot of time picking fonts and styles so things look good on a screen. I take this as saying you should supply the same type of attention to your print style sheet.

reply
I had a professor who asked us to print source code for our projects for him to read. Looks like he's still at it. I'm sure he's being driven insane in these AI times.
reply
Wild, did he ask you to use a colored printer for syntax highlighting?
reply
I program almost daily with only bold, italics and grey (for comments) in my vim rules for highlighting.

I can read my code just fine.

reply
If your beard is long and gray enough you can do syntax highlighting on the fly
reply
A well maintained beard is a pathway to many abilities some consider to be unnatural.
reply
we only had a black and white printer, I don't think they would spring for color. Also, iirc he had a script he had us run to print it, so it' not like we were printing straight from the editor.
reply
RIP vim `:hardcopy` :( .

For some harder C code (implementing `malloc` for example) my preferred debugging method was printing out the code and debugging it with a pen between classes.

I eventually realized being inside an editor gave me too much attraction to thrash with "just one more quick iteration & debug run..." and could actually end up more time consuming than being forced to reconcile my mental model with what I had already written by me double checking my assumptions.

Interestingly, some of my peers started picking up the habit for their own projects and we ended up having small "debugging" sessions by trading print-outs .

reply
This is interesting. For a while I used to print out code and debug too - more due to resource constraints: didn't own a computer, and my high school's computers were available only for limited hours per day. I used to code my first iteration also on paper - so that in the limited computer use time, I could type in the code quickly and actually see it run. Wild times but I think it made me good at programming. My friend (who did have a computer at home, but lived far away) and I co-wrote a program called "graph generator" that could plot math functions, with me doing my share on paper and giving to him to type in :) This was in the Turbo C++ IDE and since GUI based programs were unusual (at least as a project in highschool - India, 1999) it temporarily made us popular. Well, wow, that was fun to reminisce!
reply
Why would you need color to read and understand code?
reply
Source code has a structure, and some parts are more important to the reader than others. Good syntax highlighting makes the important parts easier to see; bad highlighting gives all parts the same emphasis. Notionally you could use font weight to convey this in a black and white medium, but color makes this easier.
reply
Yes. People complain about AI but the downfall of human cognition began when syntax highlighting, formatting and indentation were introduced. /s
reply
deleted
reply
You were right and your friend was wrong for not knowing how to increase font sizes on mobile. It’s actually an opportunity to teach them how to change page zoom levels in a browser. (I actually have the opposite problem: many sites make font sizes way too large and I often need to decrease zoom level.)

The only exception is that the layout of your website requires multiple columns so increasing either font size or page zoom doesn’t work well. For example gcc.gnu.org is challenging for a mobile browser if one prefers larger font sizes. You are fine if you aren’t doing that.

reply
Yeah lemme just fuck up my entire experience on the rest of the web and my phone in general to read my friend’s blog
reply
Browsers remember your zoom settings on a per-site basis. Try using it before claiming it will fuck up the entire experience.
reply
Looks like in Chrome on mobile you can set it per site, but you need to dig into accessibility for that. I don't see a way to do that in FF, so you would have to set the default which would effect all sites.
reply
> The user controls their default font size on their platform. What if they'd already increased it, and now I'm just making it bigger?

The person making the site however wanted someone to change their default font size

We have to also consider that the person in question is most likely not having a bad experience on every app and website, and that this guy just had a tiny font size on his site

Even this famously tiny fonted site is readable on mobile

reply
Most websites regardless of whether they change the browser default font size or not, do not have my preferred font size. It is my responsibility to change my own browser settings to make me have a good experience. Browser makers have made this so easy, it even remembers the setting across visits now.
reply
> I just made a simple site that didn't set any font sizes anywhere, and a friend of mine complained that the font was too small on mobile. Do I detect a lo-res screen and increase the font size?

Did you use

  <meta name="viewport" content="width=device-width, initial-scale=1.0">
That would probably be enough to look good on mobile too.
reply
Yes, I did. :)
reply
deleted
reply