200G of packages is 200G I can’t use for games and media.

Business continuity plan testing day.

I wish this wasn’t so true.

It’s cool, it’s probably just self extracting. For convenience!

Arch. Not even once.

For reals though, it’s my favorite distro because it taught me a bunch and also, once I understood that bit, it really is the only one that just worked on all my machines at the time, 15 years ago.

It’s promotion-driven development at its finest.

I use Linux because of compiz fusion cube desktop. We are not the same.

I usually think TurboTax is tracking me and selling my data to Google and others.

LMAO we really have Lemmy cliques?

Is there a language that anyone would say really does fare well for continued development or is it just that few people enjoy maintaining code? I’ve maintained some pretty old Go programs I wrote and didn’t mind it at all. I’ve inherited some brand new ones and wanted to rage quit immediately. I’ve also hated my own code too, so it’s not just whether or not I wrote it.

I have found maintainability is vastly more about the abstractions and architecture (modules and cohesive design etc) chosen than it is about the language.

Yeah, this is pretty textbook selection bias.

The real primary benefit of storing your relationships in a separate place is that it becomes a point of entry for scans or alterations instead of scanning all entries of one of the larger entity types. For example, “how many users have favorited movie X” is a query on one smaller table (and likely much better optimized on modern processor architectures) vs across all favorites of all users. And “movie x2 is deleted so let’s remove all references to it” is again a single table to alter.

Another benefit regardless of language is normalization. You can keep your entities distinct, and can operate on only one of either. This matters a lot more the more relationships you have between instances of both entities. You could get away with your json array containing IDs of movies rather than storing the joins separately, but that still loses for efficiency when compared to a third relationship table.

The biggest win for design is normalization. Store entities separately and updates or scans will require significantly less rewriting. And there are degrees of it, each with benefits and trade-offs.

The other related advantage is being able to update data about a given B once, instead of everywhere it occurs as a child in A.

Lol that makes more sense now that you clarify. I’ve heard great things about farm simulator too though. It’s certainly cheaper than a ranch.

For your actual question apparently fastfetch?

Get a remote job and do both until you know enough to quit tech?

The stupidest system is always the one I didn’t build myself. 😤

I say this in the engineering sense. I didn’t build capitalism please don’t hate me.

At least you know better than socks with sandals!

If you’re color blind enough, this could be either!

Yeah, for sure. And it’s already been forked. I have a feeling/hope that this might drive forks for some of the other popular software like consul.

Yeah, I think they meant IaC. IoC I’ve usually seen as “inversion of control” which is something else.