git changing master to main by default
The argument against the word "master" is based on the unproven assumption that the term is loaded with racist connotations, and the mandate for change is based on the fact that the possibility of the assumption's truth is nonzero and that the side-effects of the change are small.
If that were true, I would be on board with it. However, it's plainly clear that the impact of git upstream switching the default branch name to "main" is going to be huge. Many scripts with the "master" hard-coded are going to break, scripts written on the valid assumption that the name "master" was an intrinsic, unchanging property of git.
Every programmer who works with repositories before and after the change are going to constantly mis-remember which is which, and we'll have to guess at the default when working with new or unfamiliar repositories.
This event is going to establish a new epoch in git. We should take that seriously.
Which means we have to confront the fact that the assumption (that inherent racism is present in the word "master" and is causing harm to those who have suffered under racism) may not actually be true. The claims do not hold up well under scrutiny. And, as far as I can tell, the cause is championed disproportionately by white people.
The moralized nature of the question puts an external pressure on decision makers on the git project, which is normally not present for other patches. They have to consider, if they review these changes negatively, will it affect their personal reputation? Their careers? If there's even a slight chance of this, is it better not to argue the matter at all, and rubber-stamp the patches? I don't think this change is being developed under the right conditions.
On the left, we have a tendency to rubber-stamp social causes with a lesser degree of scrutiny. I think that this is a testament to how much we value empathy and solidarity, but I don't think it's a healthy way to approach our problems. Software breakage has a social cost, too.
The EU trying to ban E2E encryption:
"Competent authorities must be able to access data in a lawful and targeted manner, in full respect of fundamental rights and the data protection regime, while upholding cybersecurity.
Since there is no single way of achieving the set goals, governments, industry, research and academia need to work together to strategically create this balance. "
I like how they try to acknowledge there's no way to do it & then revert to "but try harder" anyway.
Wouldn't it be nice if any and all text presented to users by any kind of computer interface - website, mobile app, desktop app, literally anything - could be easily selected and copied to the clipboard? So that it can be pasted into translation tools, or search engines, or bug reports, or documentation? And when I say "wouldn't it be nice", I guess I mean "how is this not a self-evident truth that the industry didn't realise and achieve decades ago"? As far as I can tell, we are actively moving away from this goal, since text highlighting in websites has become ever more of a crapshoot in recent years, and is often actually impossible.
Mailing lists are resistant to censorship
#vim tip of the day: You can literally travel back in time. To jump to the state a file had 10 minutes ago, use the following command:
To then go forward in time 1 minute, use this command:
Anyone who complains about Nvidia issues on Wayland (or Linux in general!) has a moral obligation to boycott their business. Wayland developers have told you exactly why Nvidia is not supported, and who is to blame. Harassing Wayland devs because they have a name and a face you can harass, rather than boycotting the faceless multi-billion dollar company who is responsible, makes that person an asshole and a shitty consumer.
Nvidia is the one who deliberately engineers cryptographic solutions to subvert the free software driver. Nvidia is the one who refuses to collaborate with the community on standardization. Nvidia is the ONLY GRAPHICS VENDOR WHICH IS NOT UPSTREAM.
If you spent $1,000 on a GPU which became a brick when you tried to use Wayland on it, that's on YOU. Not on Wayland. Letting your confirmation bias protect your ego from the possibility that you made a mistake and turning that feeling into harassing FOSS developers and spreading misinformation about their work is FUCKED UP and needs to stop.
Took me a bit longer than I would like to admit to find out but to download a repo in sr.ht, the url is
Is there a button in the UI that I'm missing?
"We moved to GitHub because everyone's already there"
"We shut down the mailing lists because most of our users prefer to use GitLab in their web browser"
"We're rewriting in Rust because we don't really have any non-x86_64 users"
"We're leaving IRC because Discord is more user-friendly"
What all of these arguments have in common is that they exclude people, centralize infrastructure, and eschew free software for proprietary solutions, all in the name of some ill-defined measure of "progress".
Mountain biker, DevOps wannabe, full time software developer. Here to help and exchange knowledge.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!