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.
Just chilling
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.
Enterprise enjoyers today:
It’s been a long road, getting from there to here.
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.
Judging by the stars I’m pretty sure it was night time.
In fairness, the mass surveillance is just more evenly distributed when civilian dashcams are proliferated.
Best I could do:
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?
Mr holodeck-biofilter-cleaner-upper-guy 🎶
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.
You will. Because one time, 8 years ago, that exact thing happened to me and therefore I know it’s not an irrational worry. 😤
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.
200G of packages is 200G I can’t use for games and media.