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

I believe at the v6 bump something in libalpm changed and it broke the way I had installed yay, at least. Took me a bit to fix because previously I’d just installed yay with go install and IIRC that didn’t work to rebuild.

I want to say this was the issue: https://github.com/Jguer/yay/issues/1519

Oh no is my yay going to break for a week or two again?

Star spangled banner, autocorrect edition:

Oh Daddy can you see by the Dawn’s easily long What do probably we jailed add the Twilight last glowing Whoa being strips and bright state They’d the person force Or the ramparts we watched We’re so thankful streaming

And the tickets red flare The bonds busting in sure Have proof their the night That it flat was still there

Oh saw guys that day spangled banner yet and Or the leave of the few And the home of the brave

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.

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

Sandpaper remote, coming right up!

Plus you have plenty of time to tumble once or twice while your large codebase compiles.

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.

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.

I think it was big for easy local dev setups in a VM. But I think docker has pretty much taken over a lot of those use cases since a build can happen in a container pretty trivially across platforms these days. Plus be ready to deploy with the same tools, which Vagrant didn’t cover.

Formerly open source company with a few really great projects. Terraform being one of the best known. Vault is probably the second most popular unless you go back when vagrant was bigger.

I’m definitely about to deploy it at home and replace vault just to be ready.

I think they’re just trying to take over. But yes.