> I’ve never met a person saying they hate books and wish they were white on black.
That's because paper used to print books isn't always white. Most of the books I've read this year and last year had a somewhat yellow-ish tint to them (they were newly printed). I know I'm not the only person bothered by pure white paper in books.
I absolutely agree about setting brightness correctly, though. It's very usual for me to instantly reduce brightness whenever I have to use someone's computer. No idea how people use their screens so bright.
Yes, that's what's being discussed here. I'm disagreeing with the people who are defending using pure white as a background in light mode.
Pure black is more understandable, because it helps with battery life on mobile and notebooks, although I believe it shouldn't be the default dark mode.
I stopped there and had to read the answers to my comment to find out and revisit it. In hindsight, this is absolutely hilarious. Might be one of my new favorite pieces of software satire (because of how realistic, albeit absurd, it is).
> Modern languages like Zig, Gleam, and Roc offer genuine productivity benefits and attract top talent. As a bonus, their ecosystems are young enough that security tooling has not caught up yet. Dependabot will add support eventually, but until then you get the best of both worlds: a modern stack and a quiet PR queue.
How the hell is that actually a good thing? You might as well just use another language and disable Dependabot security updates if that's what you're looking for. Dependabot security updates aren't a liability, they're an asset in a world where developers use hundreds of dependencies daily, where every few months one of them is going to have a XSS or RCE vulnerability that has to be patched ASAP.
> And if you are really concerned about a dependency’s security, you can always rewrite it yourself in Rust over a weekend.
That's not how it works. Honestly, this blog post gets me really worried about this developer's projects and clients.
> If the vulnerability were critical, someone would have merged it by now.
> GitHub Copilot can automatically suggest fixes for security vulnerabilities. Instead of updating to a patched version, let AI generate a workaround in your own code.
Went right over my head LOL it actually made me angry reading it earlier hahaha
Well, that makes a lot of sense. I guess I didn't take it as a joke because I've seen some of these things recommended before (including not checking in lockfiles) in other contexts.
The "> Remove lockfiles from version control" got me as well.
> Reproducible builds sound nice in theory, but velocity matters more than determinism. Think of it as chaos engineering for your dependency tree.
Reproducible builds are nice in practice, too. :) In the Node.js ecosystem, if you have enough dependencies, even obeying semver your dependencies will break your code. Pinning to specific versions is critical.
You wouldn't believe how many of these things I've seen seriously recommended before. Also, I do have difficulty detecting sarcasm sometimes (even though I'm very fond of it).
To solve this, I personally simply wait a few weeks before updating Fedora versions! Generally that's a good idea not only because of RPMFusion, but specially because of the multitude of GNOME Extensions I use, some of which take a bit longer to update whenever there's a new GNOME release.
It's a community repository for Fedora. It works similar to RPMFusion: you can use it along the official repositories to grab software that's not available there. If you'd like to reduce the number of organizations you're directly depending on, you may choose to use their Fedora fork, with their own repositories (forked from Fedora's), called Ultramarine Linux [0].
This might now be one of my favorite websites in the internet. It won me when I saw the "Excel Backend" design pattern [0]. I wish so fucking much I had never seen this before or heard of using Excel as a database.
update: I'm feeling actual physical pain by reading this and remembering every single piece of software or website I've seen that actually applies these patterns [1].
Unfortunately most of the content hasn't been updated for two years straight, which is quite a lot considering how much ECMAScript and TypeScript have been changing in recent years. I guess it's still a good reference, though.
Darktable is the best photography editing and classifying software I've ever used. New users should be warned it's quite power-user centric though. Adopting isn't like opening up Lightroom and messing around. You may have to read a bit of documentation regarding the modules and different workflows (i.e. Sigmoid vs FilmicRGB).
I think the Ansel developer has a YouTube series with tutorials on how to edit in Darktable using the Filmic RGB workflow. Not sure if that's where I'd get started nowadays (I've just adopted Sigmoid and it's way quicker to edit with it), but it gave me a solid base in how to use this software.
For some reason, there's a huge amount of Hacker News readers who are still full-time Windows users. With the forced migration to Windows 11, I guess a lot of them are now not only trying out Linux for the first time (as a desktop system), but also for some reason going for Arch derivatives, which is always fun to see a beginner mess with LOL
I absolutely agree about setting brightness correctly, though. It's very usual for me to instantly reduce brightness whenever I have to use someone's computer. No idea how people use their screens so bright.
reply