

The phone space is ruled by apps. The phone makers and the companies developing apps prefer it this way.
That’s true, but for everything non-free, they always end up having a perfectly working web app that will accept my money.
The phone space is ruled by apps. The phone makers and the companies developing apps prefer it this way.
That’s true, but for everything non-free, they always end up having a perfectly working web app that will accept my money.
I mean, there are many excellent open source malware.
The ??? Is mostly phishing campaigns, I think.
Special shout out to the person who committed a gigabyte memory dump a few years ago. Even with a shallow clone, it’s pretty darn slow now.
If you want to be the team’s hero, I’ve had good luck removing old commits using git filter repo
.
https://hibbard.eu/erase-sensitive-files-git-history-filter-repo/
We can’t rewrite history to remove it since other things rely on the commit IDs not changing.
Oh right. Oof.
I would be working to arrange an accident for those other things. Those other things probably need to be retired.
The point is that when we look at what this God supposedly created, they’re clearly enthusiastic about all kinds of wild spectrum of sexuality.
On days when I entertain the possibility of an infallible text, I’m not so sure I got the exact right version that I’m ready to deny someone else’s lived experience. I would have to be incredibly sure to be willing to gaslight someone else.
On more frequent days when I don’t subscribe to an infallible text, I find it pretty clear that God created and adores all kinds of wild sexuality, and their message to humanity suffered badly under some seriously bigoted editors.
Oh shit. We’re not supposed to open those?
When I’m not using git reflog
, it is only because I a’m not making big enough git
screw ups.
Is it ok to continue on a branch if you also merge back main into it?
On some repositories, sure.
But better maintained repositories don’t allow merge commits (because merge commits suck), and so will have squashed (or rebased) on merge.
(If squashed) The squash will have changed commit IDs, so a long running branch rebased won’t benefit from a clean shared commit history.
So it can work, but “you’re gonna have a bad time.”
In general, git works best if branches are thrown away as soon and as often as possible.
(Edit: Good clarification in response below, added here for consistency and accuracy.)
politicians are very stupid when it comes to tech it seems.
They are so so so stupid, about this.
There will be so much blackmail and ruined political careers if these backdoors get installed.
A backdoor is never solely used by the folks one might hope would use it.
Ah hahahahaha. Ah hahahahaha. Hahahaha-aaaack! Thump
I agree. That is Inconceivable.
But, I feel obligated to add:
“You keep using this word…I do not think it means what you think it means.”
Except when adding the log fixes the race condition.
(ノ`Д´)ノ彡┻━┻
The most famous is: never get involved in a land war in Asia. But only slightly less well known is this!:…
Well, here’s a sentence I haven’t been tempted to use before:
“I believe that may be too many crontab entries.”
This is so true.
I recently had a colleague - ignorant of this perspective - give a training presentation on using AI to update a kind of bullshit job useless document.
Dozens of peers attended their presentation. They went on demonstrating relatively mindless prompt inputting for 40 minutes.
I keep remembering just how many people they shared their AI enthusiasm with.
I think they may honestly believe that AI has democratized the workplace, and that they will vibe code their way to successful startup CEO-ship in a year.