technom

Solid state physics.

Gitlab is very complex and a heavy resource hog. You probably don't need it. Most small to medium enterprises can comfortably host their projects on lightweight forgejo or gitea (speaking from experience). They even have functionality similar to github actions. If you need anything more complex, you are better off integrating another self hosted external service to the mix.

Oh man! I hate CF! The scummy gatekeepers.

He didn't just wash off his hands. When asked in an interview about a moderator who edited a trans user's profile to intentionally misgendering them (yup, even that's not off limits for their mods), he justified it saying that 'It's not like using the N-word or something'. (For context, the n-word itself was innocuous. It gained notoriety due to its misuse by bigots like this).

There are several such examples - repeatedly even after being called out. I don't belong to any diversity groups. But I don't care if they make the world's best operating system. I will stay well away from it if only to avoid any interaction with such a group. They're a bit too happy about harassing people (not just transgenders either).

This is clearly intended as an alternative to submodules.

An alternative, not a replacement. Vdm is specifically designed to track code dependencies. There are use cases like monorepos where vdm won't work.

Neither does Git though. I’m not really sure I follow your point.

Git does track submodule history unlike vdm.

By default, vdm sync also removes the local .git directories for each git remote, so as to not upset your local Git tree.

Git submodules don't delete those .git directories. It uses them.

If you want to change the version/revision of a remote, just update your spec file and run vdm sync again.

This is not how git submodules or subtrees work.

vdm does depends on git being installed if you specify any git remote types

Support more than just git and file types, and make file better

Git submodules and subtrees don't support anything other than git remotes.

Yes. I saw that. I was giving you my assessment based on the rest of the technical details in that readme. It doesn't look like vdm is dealing with any part of the dependency repos (.git directories) other than to download them. In fact, they even mention deleting those .git directories. Please let me know if you think I misinterpreted any of those details.

That makes me wonder! All these new GPU uses are enormous energy hogs. Is gaming like that too?

Arch guide expanded in scope IMO. The choices are way more than in the past. However, it's good quality and easy to read. I implore you to skim it, even if you don't try it out.

Nvidia is a mess on Linux in general, though it's gradually improving. They decided to neglect everything that the other GPU manufacturers and the community were doing and roll out their own buggy concepts.

This really isn't the fault of Mint. PopOS works with it just because its developers System76 also has a line of nvidia based hardware. However, as I said before, nvidia is slowly starting to implement the standards and situation on other distros like Mint will gradually improve.

Meanwhile, I'm curious. What hardware did you try Mint on?

It didn't look like a submodule reimplementation to me. Subtree is more of a submodule reimplementation. This is more like a language-agnostic package manager (like cargo, npm, etc) that downloads and caches source packages.

I wonder what happened to Tails - the one that started it all.

I do recommend Gentoo (haven't tried Funtoo) for the academically inclined. It's a beast to maintain, but you'll soon find yourself at ease with configuring and compiling your own kernel, configuring your packages and even making some yourself.

It isn't as hard as people make it out to be - if you gradually push your boundaries. In particular, it's good if you already use Arch.