TechNom (nobody)

Solid state physics.

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.

Is it legal? There may be alternatives with plausible deniability.

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.

While I understand your point, there’s a mistake that I see far too often in the industry. Using Relational DBs where the data model is better suited to other sorts of DBs. For example, JSON documents are better stored in document DBs like mongo. I realize that your use case doesn’t involve querying json - in which it can be simply stored as text. Similar mistakes are made for time series data, key-value data and directory type data.

I’m not particularly angry at such (ab)uses of RDB. But you’ll probably get better results with NoSQL DBs. Even in cases that involve multiple data models, you could combine multiple DB software to achieve the best results. Or even better, there are adaptors for RDBMS that make it behave like different types at the same time. For example, ferretdb makes it behave like mongodb, postgis for geographic db, etc.

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.

Nobody ever learned from the solarwinds attack. If a massive amount of your infrastructure is backed by some obscure software, bad actors will either try to insert a backdoor or find a zero-day exploit. If people are going to neglect what just happened, crowdstrike will fall heals up, faster than solarwinds did.

I don’t think that rust would have prevented this one, since this isn’t a compile time error (for the code loader).The address dereferencing would have been inside an unsafe block. What was missing was a validity check of the CI build artifacts and payload check on the client side.

I do however, think that the ‘fingers-crossed’ approach to memory safety in C and C++ must stop. Rust is a great fit for this use case.

Why are sensitive or critical hospital systems loaded with bossware? That itself is a breach of medical safety regulations and medical privacy. If such bossware fails for whatever reason - even sabotage, it’s on the leach class. Prosecute them for murder.

Crowdstrike exists for Linux too. In fact, it apparently crashed RHEL and Debian a few months back. That didn’t get so much attention.

Falcon seems to be a cross between an antivirus and an intrusion detection system (IDS). There are many antiviruses on Linux, but only one FOSS AV is popular - ClamAV. As for IDS, snort is an example.

But in the true sense, Falcon is much more than just an AV and IDS. It’s a way to detect breaches and report it back to CrowdStrike’s threat detection and analysis teams. I don’t think there exists a proper alternative even in the commercial sector.

In that case, it’s time for the average workers to sabotage the bossware. Let the leech class solve the problem they create.

Google has discovered that FOSS software under their full control is better than pure proprietary software for monopoly abuse and rent seeking. With FOSS software, they enjoy the automatic popularity that they otherwise would have had to market very hard for. At the same time, none of Google’s free software is truly free. Google devs regularly neglect and reject overwhelming user requirements (jpegxl in chrome is probably the best example of this) and choose designs that clearly favor the company monetarily. It isn’t even practical for normal people to fork their projects.

Google often uses their ‘FOSS’ projects to twist open standards or the market to their advantage. Android and Chrome are very significant players in this regard. Using Chrome, Google even managed to make the W3C standard too complicated for others to make alternative browsers easily. Google has similar ambitions in the multimedia market. They want to replace the monopolistic media formats with quasi-monopolistic formats like webp and av1 instead of truly open ones like jpegxl.

It’s still possible on almost any distro with pyenv or asdf-vm.