

Hmm, I don’t have too large of a sample size, but I don’t feel like Ruby programs are buggier than Python programs, on average. Not being the language for programming beginners and data scientists, probably aides that impression, though…


Hmm, I don’t have too large of a sample size, but I don’t feel like Ruby programs are buggier than Python programs, on average. Not being the language for programming beginners and data scientists, probably aides that impression, though…
Since no one mentioned it yet, this is the classic card game “Klondike”.
KPatience is a program that implements multiple such card games…
A few years ago, I learned that the stomach rumble when you’re hungry, is part of a process that’s actually kind of important health-wise: https://en.wikipedia.org/wiki/Migrating_motor_complex
So, it’s good when your stomach and small intestine empty out on a regular basis. It’s good when you’re hungry on a regular basis.
Just yet another luxury problem of modern times, that we have food available at all times and need to stop ourselves from snacking.
Side-note: It’s also good to go hungry, because then when you do eat, the food tastes so much better. This also means you can go for healthier food and still have it hit the spot.
It’s somewhat of a vicious cycle, too. When you do a hobby, you typically achieve stuff, whether that’s inter-personal relationships, a painting you wanted to finish, or e.g. physical fitness.
These successes, as well as their knock-on effects, help to form long-term happiness. With mindless media consumption, on the other hand, the happiness stops pretty much as soon as you turn off the screen, so you have to keep going back for more, and then it also takes time away from forming long-term happiness.
Hmm, good question. I know of one such implementation, which is Delta RPM, which works the way I described it.
But I’m not sure, if they just designed it to fit into the current architecture, where all their mirrors and such were set up to deal with package files.
I could imagine that doing it rsync-style would be really terrible for server load, since you can’t really cache things at that point…
Had to search for a bit, too, but finally found the relevant keyword: Delta RPMs
(Which also explains why it’s a Red Hat / SUSE thing. 😅)
Here’s a decent article, which links to some more in-depth explanations: https://www.certdepot.net/rhel7-get-started-delta-rpms/
This doesn’t work too well for rolling releases, because users will quickly get several version jumps behind.
For example, let’s say libbanana is currently at version 1.2.1, but then releases 1.2.2, which you ship as a distro right away, but then a few days later, they’ve already released 1.2.3, which you ship, too.
Now Agnes comes home at the weekend and runs package updates on her system, which is still on libbanana v1.2.1. At that point, she would need the diffs 1.2.1→1.2.2 and then 1.2.2→1.2.3 separately, which may have overlaps in which files changed.
In principle, you could additionally provide the diff 1.2.1→1.2.3, but if Greg updates only every other weekend, and libbanana celebrates the 1.3.0 release by then, then you will also need the diffs 1.2.1→1.3.0, 1.2.2→1.3.0 and 1.2.3→1.3.0. So, this strategy quickly explodes with the number of different diffs you might need.
At that point, just not bothering with diffs and making users always download the new package version in full is generally preferred.
openSUSE Leap does have differential package updates. Pretty sure, I once saw it on one of the Red-Hat-likes, too.
But yeah, it makes most sense on slow-moving, versioned releases with corporate backing.
The thing to me is always that, yeah, you need a huge commit for a breaking change in an internal library inside a monorepo, but you will still need to do the same work in a polyrepo eventually, too.
Especially since “eventually” really means “ASAP” here. Without going through the breaking change, you can’t benefit from non-breaking changes either and the complexity of your codebase increases the longer you defer the upgrade, because different parts of your application have different behavior then. So, even in a polyrepo, you ideally upgrade all library consumers right away, like you’re forced to in a monorepo.
Good question. My best guess is that the buttons have become less important, because:
But yeah, I got a new monitor at work, and instead of buttons, it has a joystick on the backside. Now the monitor’s menu pops up every so often, I’m guessing because something shook the joystick just enough to trigger it.
When I saw that joystick for the first time, I wondered how long it’ll take before it breaks, but it’s broken on day 1, so that’s great. 🫠
I believe, the problem is mainly white bread, which is what people typically have in mind for feeding ducks.
As opposed to wholegrain, it only retains the endosperm, which is mostly just carbohydrates without many nutrients:
![]()
I think, the lack of fiber is also particularly problematic. At least, I’ve heard that it gives them diarrhea, which probably means their guts don’t have time to extract the few remaining nutrients.
Spidey does appear to be pregnant in panel 4, so…


No idea, but I have not yet heard of a computer science department going exclusively for Apple…


Probably varies a lot between countries and universities. In my university, you were better off, if you were on Linux. But I’ve heard horror stories from the US before, where Windows was mandatory…


Yeah, the headline makes it sound like he’s insulting AI, but he’s just illustrating a fairly basic fact…
It shows up as “Terminal” in the search results, so I imagine that’s what it matches against, even if it is colloquially referred to as “Windows Terminal”…
On KDE, it’s just one of the suggestions, I believe, that you could search this term on the web. If you trigger that suggestion, it then opens the web browser to do the search.
As such, searching “terminal” wouldn’t yield a suggestion from a web result that matches, but I’m pretty sure applications are prioritized above other results either way.
A few years ago, I set up a home-server with music and some pictures on there, and recently I noticed that my storage disk was getting full. Then I saw that the disk only had 16 GB and wondered, where the hell I got that small of a disk from.
So, I go to plug in a bigger disk and can’t even find the original disk at first. Turns out my whole storage capacity was one of these bad boys:

And yeah, I’ve got about 1800 songs, clocking in at 5.8 GB, so even that tiny storage would easily be enough for a much larger collection.
And I do also have them replicated on my phone, for listening on the go. (Don’t even need an SD card in my case.)
Man, I haven’t done structural inheritance in years and by now, this reads like the ramblings of a mad person.
Like, I recently had a use-case, where I actually wanted to define multiple types with the same fields and for various reasons ended up using a macro for that.
And that still felt simpler than whatever is going on in this article, because there were no cross-relationships between the types at runtime. The macro templated the type definitions as if I had copy-pasted them, except there’s no actual code duplication, which is ultimately all I wanted.