Just chilling
Voltages drop in the cold, and the middle of the night is usually the coldest. So that’s why this is probably not far from reality.
Business continuity plan testing day.
I wish this wasn’t so true.
LMAO we really have Lemmy cliques?
Sandpaper remote, coming right up!
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.
Nonsense! We will write that history so that we’re clearly the good guys!
Unless you’re saying it’s possible we’ve not always been the good guys but surely that’s not it.
Or then you type the next letter of the word and the result you want goes away, but only after you’re milliseconds from tapping it.
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.
Actually it’s Admin47 now because of the yearly password change requirement.
I’m not saying it doesn’t suck for this person, but product market fit is a thing for open source too. If people need it they’ll use it and contribute until something better comes along. If not, your idea wasn’t the one. That doesn’t mean it’s not possible. Nearly my whole life runs on open source software, so it’s pretty clearly sustainable.
over the years, using “open source” has become an excuse to avoid paying for software
Um. Yes. And to be blunt: obviously. And in return, I give away software I create for free whether people need it or not, and try to give back in the form of contributions too. But I’ve never once given up my day job for it. Would that be nice? Maybe. But open source software is more frequently sustained by passionate people using and expanding it for their own projects and not by expecting people to pay you for your efforts when you’re likely not paying (nodejs, github, ahem) for the software you’re building it on anyway.
Yes we’ve had proxy war. But what about second proxy war? And elevenses?
I ordered them through Lowes and they had all sorts of options for connectivity and power, including just old school chains. Looks like they’re Bali brand.
Haven’t watched the video yet, but I’m a huge fan of our plug-in z-wave smart blinds. Makes getting all that extra light way easier and automatable.
Piracy is just staying over at a friend’s house.
TBH I use that to make sure my kids brush their teeth before the electronics get Internet in the morning.
I mean. “she was killed by the IDF” is passive voice, no? I think IDF is out of control as much as the next person but passive voice can be communicative and clear as much as active voice. And clearly it’s easy to reach for if you gave it as a counter example accidentally.