I wish this wasn’t so true.
Just chilling
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.
LMAO we really have Lemmy cliques?
Sandpaper remote, coming right up!
It’ll probably be stored in something like a TPM, whose primary purpose is to make intact extraction of the keys difficult or impossible. A few keys might become compromised but in this scenario (unlike DRM decryption) it’s easy to ignore those keys. There’s always the chance an exploit becomes available and is more widely used, though, in which case it would definitely be less valuable.
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.
Huuuge… Tracts of land.
Judging by the stars I’m pretty sure it was night time.
At least you know better than socks with sandals!
If you’re color blind enough, this could be either!
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.
A few days of my pain in exchange for months of glory and beyond.
Well my owner is definitely getting his money back or starting a class action suit for false advertising.
Yeah, the image (not mine, but the best I found quickly) kinda shows a rebase+merge as the third image. As the other commenter mentioned, the new commit in the second image is the merge commit that would include any conflict resolutions.
Merge takes two commits and smooshes them together at their current state, and may require one commit to reconcile changes. Rebase takes a whole branch and moves it, as if you started working on it from a more recent base commit, and will ask you to reconcile changes as it replays history.
I’m pretty sure they blame the others for not being more careful and that they if only they slipped and fell more often it wouldn’t hurt so much.
Yes and then they get drenched and track it all over the house causing others to slip and get hurt.
Business continuity plan testing day.