Oh, I am certainly aware he is a massive cunt. The juxtaposition only edifies Geerling even more, honestly.

I’d say there are better tech youtubers out there that you should watch instead, such as Jeff Geerling. https://www.youtube.com/channel/UCsd6hP-zzIkCpw8XGw7Osyw

Are the headphones usb-c? Because those cheat and are actually a whole sound card in a chip

AGPL is GPL + network services protection (preventing someone taking your code and spinning up a for-profit selling services without contribution back). If you don’t care about people stealing your code, closing it, and selling services based on it, then there is no need to consider strict copyleft licenses.

ugh, a sequel to that perfect game would be awful

To be fair, I think those devs have a good idea on how a content-addressable-filesystem-cum-blockchain should work. The primary use-case, Linux kernel development, has very particular needs such as being distributed, allowing complex merge strategies, and being aggressively transparent. That the rest of the world then adopted this particular (D)VCS was mostly an accident.

Back in the before times when git was first new, I was an avid supporter of svk (a perl hack that bolted on distributed qualities to svn). Very useful to have complete server state locally especially for merging. svk worked, but had a lot of foibles, being the hack that it was. When I finally pulled the trigger and migrated repos over to git, even those early versions, reduced the complexity of my setup dramatically. Haven’t looked back since. The porcelain of git has improved dramatically over the years (even if I still use git checkout -b). But it is still very much an expert tool and most users don’t engage deeply with it. Which is exactly what the blog post recognizes and laments because the supposed experts aren’t.

Most projects do not need the complex merging capabilities of git. I’ve found that simply structuring the workflow around trunk based development with linear history works the best: short lived feature branches that get rebased/squashed/committed and the tip of main is always deployable. It avoids dealing with all of the bullshit that comes with long-lived branches and migrating changes between them. This also requires structuring the work itself if you have a larger team so that if you are all working on the same system, avoid crossing the streams (draw some boundaries) to keep dependencies between branches at a minimum. When it starts getting into stacked patches, that’s a good sign you have a kink in the review pipeline somewhere and this complexity can go away with some managering. Git is as complex as you want it to be, and pretty easy to keep it simple

Huh, so a water balloon launcher with some sharp rocks can probably make sure they understand this was a bad idea

If you look at the network on that repo, there are some newer forks: https://github.com/Alkarex/EasyRSS/network

With the clankers these days, if you wanted to do your own build, that is completely within reach

I think they are using NMS as a platform to try out new tech, too, for other games. All of the “recent” ship building stuff where you can basically take your carrier down to a planet was mentioned as being this

I feel like every time I’ve gone looking for an info page, it was just the man page content, but now I’ve got some useless shit I installed.

I mean, maybe this is a debian thing.

What’s worse, is if this is GNU-ware, there is a good chance the answer IS NOT IN THE MAN PAGE. I think it was bash or maybe gawk. I don’t remember exactly, but I had a question that simply wasn’t answered in each man page. GNU docs are absolute trash, written without any consideration for the audience.

Matrix will sadly never be a thing, much like XMPP never really became a thing (well, it was a thing until google pulled a play from the 90-00s era Microsoft of Embrace, Extend, Extinguish). And each of those tried to replace IRC which still works and is perfectly fine.

Five years? My, aren’t we optimistic.

At the same time I’m kind of shocked how much of these emails happens on seemingly regular @gmail.com or @yahoo.com addresses.

So much for Snowden’s revelations about PRISM. All that digital surveilance and yet they don’t catch the pedos and traffickers with it. Curious.

They need standing desks, obvs.

Exactly. You’re responsible for the code that is submitted. I’ve seen good code come out of proficient centaurs. These are the peeps that know their craft well and can make the robots dance their tune. I’ve also seen shit code from people that obviously didn’t read the output too closely, and let the robot go off the rails. The latter group is who needs to be strung up from the rafters.

When you do fix it, the internet would appreciate a follow up comment on what you did to fix the problem

Sounds like your /etc/fstab is wrong. You should be using UUID based mounting rather than /dev/sdXY. Very likely you’ll need to boot from a usb stick with a rescue image (the installer image should work), and fix up /etc/fstab using blkid

Vibecode something? Fair warning that vibecoding android apps is fraught with peril. Be very explicit in what versions of android and the SDK in your prompt.