Good butter straight from a dairy farm is super dangerous though. You can suddenly find yourself standing in your kitchen, no memory of the last 45 minutes, the fridge door open, a greasy knife in your hand, breadcrumbs all over the floor, and half the butter gone. Gotta be careful with that stuff.

Connecting to the network does not have to mean connecting to the internet. Basically every consumer grade router out there is capable of restricting a device to the local network only. It could reach other devices on the network and the other devices would be able to reach it, but it would still be cut off from the internet.

Yeah shit tends to look worse when you zoom in, compress, and drop a whole bunch of frames.

I don’t think anyone sees one single old scar and thinks self harm.

Widewine? Maybe they have some content that requires L1, which still doesn’t work on Linux because of totally legitimate technical reasons that are absolutely not at all utter horseshit. Or they might be using some browser APIs that are not properly supported on Linux. There are a few of those.

If by “literally anyone” you mean any catholic man, then sure.

Is that the guy who was stabbed in the anus by a toilet child climbing up the poop chute?

Past experiences

So that the toddler can enter the workforce and start pulling itself up by the bootstraps as soon as possible. The lithium mines need more bodies.

I once worked on a project where the main function would run the entire code in a try-catch block. The catch block did nothing. Just returned 200 OK. Didn’t even log the error anywhere. Never seen anything so incredibly frustrating to work on.

Mostly the latter. We don’t do any optimizations on our product whatsoever. Most important thing is to say yes to all the customers and add every single feature they want. Every sprint is spent adding and adding and adding to the code as much as we can and as quickly as we can. Not a single second is allotted to any discussion about performance or efficiency. Maybe when something breaks, but otherwise we keep piling on more crap at full speed non-stop. I have repeatedly been told “the fast way is the right way” followed by laughter. I was told to “merge this now” on multiple occasions even when I knew that the code was shit, and told the team as much. I am expected to write code now and think about it later.

As you can expect, the codebase is a bloated nightmare. Slow as shit, bugs galore, ugly inconsistent UI, ENORMOUS memory use, waaaaaay too frequent DB access with a shit ton of duplicate requests that are each rather inefficient themselves. It is a rather complex piece of lab management software, but not so complex that it should be struggling to run on dedicated servers with 8 gigs of RAM. Yet it does.

The why is easy. As others said, the vast majority of error messages are entirely useless for you, the user, because there’s not a single thing you can possibly do to address it. What are you gonna do about a database connection issue, or bad cache, or broken Javascript? Nothing. So don’t worry about it. Besides people are less panicky when they see an oops rather than a stack trace or a cryptic error message.

And don’t worry, people who know how to write up useful support tickets and bug reports know how to do it even when all they can see is an “oops”. Builtin browser dev tools will have information they can use to help the devs.

Could be fun.

Long ago, the 118 nations lived together in harmony. Then, everything changed when the Ytterbium Nation attacked.

For your next assignment, try to get them to draw images of analog watches that show something other than 10:10.

The results of any search engine.

Reddit.

Lemmy.

This really is not a rare thing. At all.

Why wouldn’t they? Links did not stop turning purple, this still happens very often.

I have node named pve too. Small world.

They could be, but that wasn’t standard behavior. When laptops started to become a thing it was realized that having hot swappable peripherals made too much sense to ignore, so some devices had improved ps/2 ports and controllers that could do that.

Twice, because usually it’s two sticks.

In any case, RAM failure is rare enough that quadrupling its chances is not gonna make any meaningful difference. Even if it does, RAM is the easiest thing to replace in a PC. Don’t even need to go offline while waiting for a new stick. Someone who’s got the cash to build that thing in the first place won’t be too upset by the cost of another 32gb stick either, I don’t think.

Of course not. You need other software to rip your music from physical media, or potentially multiple other software to search and download them. You’ll need additional software to host everything over the internet. You’ll probably want a computer to act as a server. You’ll very likely need a private VPN to be able to access it over the public internet. You’ll need some networking knowledge to set everything up. Hope you’re familiar with docker. And afterwards you’ll have to manage everything yourself once they are up.

Even if you don’t search for new music very often it’s a lot of work. If you care about being able to discover new music then it’s pretty bad. There’s a reason music streaming exploded in popularity so quickly. This shit is not easy or convenient to self-host. At all. If you’re already selfhosting a bunch of stuff, then it might be worth it to add this stack on top of your existing stuff. But absolutely not worth building anything from scratch just for this.