The devil is in the details.

Sen. Richard Blumenthal, D-Conn., asked Noem whether Lewandowski has “a role in approving contracts” at DHS. Noem responded with a flat denial: “No.”

“But is he doing it anyway?”

Probably because it’s not illegal.

When you open and read files from a program the OS (kernel) will typically cache part or all of those files in memory. This is to speed up subsequent reads of that file since disk access is slow.

“preload” seems to be making use of that feature.

The kernel maintains this cache and evicts (unloads) things from it as needed. You don’t need to worry about it.

Gonna make provisioning servers a lot more interesting…

Their community still a cespool?

Man, what’s up with Linux filesystem developers?

Compared to checks notes reinstalling an entirely different distro???

Jesus the cli phobia here is ridiculous.

While learning about all the Linux stuff I came to know about desktops, and I felt like, if I wanted to ever use a different one, yes, it could be installed the hard way, but I would rather have a distro that can be installed with my desired desktop by default, and the one that got my attention was KDE.

‘sudo apt install kde-full’ is “the hard way”?

No shit. Why would they even say that?

Ahhh, self doubt, my old friend…

“There is probably a better way” is a fairly common feeling. In fact there probably is a better way. But at some point you need to be pragmatic and be happy with “good enough”. Don’t let perfect be the enemy of good (enough) as they say…

That said - follow your intuitions as well that things could be done better. Don’t be afraid to just re-write a bunch of things to see if an idea works better. Like grouping things from some “common.php” into domain specific functionality (dates.php, db.php, etc.). Or re-working how your front-end works. Maybe read other code or ask for code review from people more experienced, or even from an AI (yes, yes, I know, but they can be useful).

One problem you can find yourself in is that you’ve created code that’s very difficult to understand, but since you’re “in it” right now you understand it completely. If you put the code down for a week or two and come back to it you may find it very difficult to re-learn. If using classes, creating a DAO layer, or some other pattern helps to make your code easier to read then it’s worth following.

Maybe we stop using it as an identifier as it was never supposed to be?

Man, what a stupid idea .DS_Store was.

Yeah - that’s why I was careful to say “most”. Stay away from weird “immutable” shit.

The “multiple distros thing” is often the most confusing aspect of the Linux ecosystem. But don’t sweat it too much - they’re more similar than different. Generally speaking you can do all the same things with most any distro.

The most user-facing differences are in the installer, default UI settings, and how applications are installed. A lot of it is simply preference.

All of the ones you mentioned are “fine”.

But if you want to “distro hop” (something that I consider to be a mostly pointless activity) then you need a way to preserve your home directory between installs. It’s where all of your settings are kept. The two ways of doing that are typically a) have a backup somewhere (recommended regardless) and b) put /home on a separate disk partition (more advanced - easily Googleable though).

Wow - I applaud the effort but that’s… a lot.

I have frequently used notebooks to sketch out high-level ideas and designs which in itself seems to be a rarity. But at the “It’s detailed enough that someone else could come along and replicate the steps” level is unfathomable to me.

Having to write out what I’m going to do on a physical medium is orders of magnitude slower than typing it out and would just take ages. Maybe it’s just a lack of discipline thing but for me coding is a ton of trial / error / re-write. I refactor code constantly. But it has inspired me to maybe keep more of a log “generally” for things I’ve been working on. It can be useful to be able to refer back to notes rather than needing to dig through emails or git logs hoping to find some rational for a decision…

They appear daunting, but the simple edits you’re talking about aren’t very difficult to do. I’ve used kdenlive for simple things and it’s pretty easy to learn. Your may just take a little Google for the first run through.

Sorry, I mean “it simply doesn’t work”.

And then when he try actually tries it everything breaks and he spends hours trying to get udev working from a distrobox container.

Good luck getting an admin to register your Windows VM with Active Directory.

Christ, it’s going to look like baroque France vomited all over it when he’s done isn’t it?