![](https://lemmy.stuart.fun/pictrs/image/910b6b99-09cf-4901-ba16-a9b3fff89e56.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
I wish this wasn’t so true.
Just chilling
I wish this wasn’t so true.
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.
Oh man, they’d be super offended by your comment if they could afford Internet. And read.
Elon musk surprised shareholders with this HOT investment trick.
I usually think TurboTax is tracking me and selling my data to Google and others.
LMAO we really have Lemmy cliques?
If it disproportionately affected non-white or poor people.
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.
There were 12 of these angry dogs, though. Not one trusting dog in a cinder pit. I don’t know if Noem would have been able to handle it even with a gun.
Yeah, this is pretty textbook selection bias.
In this economy I’m going to settle for a used threeskin in the next year or two.
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.
Well, when you’re a star, they let you do it. You can do anything.
Forest food in the form of more sunlight from reduced smog lol.
Actually it’s Admin47 now because of the yearly password change requirement.
Chilling with bears, if I understand recent events correctly.
In my experience, bad neighbors don’t really move. If you’re lucky, you can move. But yeah, the qualities that make them bad neighbors often follow them to the rest of their lives, and they’re stuck at their current means and especially in this economy, that’s not a recipe for moving.
Some people see the value in trying. But yes, sometimes it’s hopeless.
That sounds like a great question for the highest court in the country. Wait a minute…