@colinstu I don't think you should feel bad for putting your mental health first. I learned the importance of being careful quite a while ago when I was following way too many people and the constant discourse and hot takes dragged me down.
Nowadays, I only follow if I'm pretty sure I'm going to like someone's posts, and I unfollow if it turns out I don't. Following doesn't mean anything beyond that to me, and I'm also fully aware that people won't like everything I post, so I won't judge anyone for giving me the same treatment. Heck, I never even look at my followers list and have no idea how many I have.
@xarvos@Notsonoble Ooh, I get it. When I say "no limit" I usually assume "max-width: 100%" as a fallback because there's really no reason not to do that.
@xarvos@Notsonoble I'm not sure what you mean by jiggling left and right. If the viewport becomes too narrow code blocks should of course be only as wide the other other content on the screen.
@xarvos@Notsonoble Yeah, you can scroll them. Horizontal scrolling is pretty annoying, though, so if it were up to me I'd make code blocks wider to make sure most code fits nicely.
@Notsonoble Personally, I handle code blocks, tables and some other elements by allowing them to be wider than the limit. They aren't body text so there's no reason to have a limit on them, and I'm also not a fan of the issue you're pointing out. Wrapped lines would look pretty messy as well, so lifting the limit for code blocks would be the best solution.
GNU doesn't make good use of the web format, that's true. It's probably intended for print so they can't include fancy menus. The font is fine to me, but it looks like it chooses your default font for sans-serif. Mine is set to be Inter (would recommend).
I'll give you a more modern documentation which does use the horizontal space nicely while keeping the content at a comfortable width: docs.astro.build/en/concepts/why-astro/
The FreeBSD docs are okay, but they need a way larger line height. A factor of 1.8 is typically considered good at that line width, but it only uses 1.5.
@Notsonoble Shouldn't the readability be the deciding factor? What use is a manual if I keep stumbling over the text because the lines are too long? I checked some online documentations and they limit the content width all the same, e.g. www.gnu.org/software/make/manual/make.html
My boss wasn't happy about me using libraries such as Zod to define interfaces because it looks confusing. To be fair, it does look like shit compared to native interfaces from other languages.
But I can't get rid of it because things like Date objects are converted to strings when put into JSON, and then my regular TypeScript interfaces would always be wrong for either frontend or backend.
I get now why some web apps send JavaScript code around. Shit would be so much easier.
If you look at my website, you'll see that it's usually very wide. The art section is completely unbounded, even. But the notebook area with the text? Narrow because believe it or not, I actually care if people can read it.
I can't stand overly airy mobile-first designs that make you scroll like a maniac either, but at least try to think if what you want is actually reasonable.
What's the point of cramming as many words as possible on the screen if the readability drops by orders of magnitude? Boy, I sure am glad I can look at all these words, though. AAAAAAAAA
People who go "the new layout leaves so much empty space on the sides " are the bane of my designer existence. There are things you can scale horizontally, and there are things you can't. Reading wide text SUCKS
Volpeon