You've completely submitted to big oil PR and you want to talk this shit? Cope harder.

There is no direct equivalent to DLL hell on Linux because nothing precludes you installing multiple different versions of a library and loading them at the same time like DLLs. But if you go trying to get a new version of some software on Debian that nobody has bothered to package yet, you will often have a bad time. You will need to build dependencies for your dependencies and then you will need to build dependencies for those dependencies and so on. You can help keep your system clean by setting the prefix someplace in opt or whatever and installing all of them to their own tree, but then you will also find that some of them have config files that you're going to have to change the locations for so that they don't conflict with other versions of the same deps you've got installed and so on. The more complex the package the more of this you will deal with as it will have more deps and those will have more deps and so on.

No, it isn't. I mean, it's not the same line of thinking. Systemd does only exist because of redhat. It doesn't solve any problems because there are things you can't do in unit files, so what you wind up having is unit files that cause systemd to call shell scripts, at which point you have gained nothing.

Snap, as shit as it is, addresses a real problem in a way that at least offers a solution to the problem. Systemd addresses a made-up problem in a way that doesn't even solve it. The only thing the two have in common is that they both create new problems.

It's not all automated though, there's a puppet master. Well, not master, they're very far from mastery, but I think you get what I'm saying.

We should have been planting trees and switching our high emissions ag over to lower emissions types because nature had reached relative stasis before we got to this point but after we became aware of the problem, as nature already had evolved mechanisms to fix the problem which we could have made use of. But now it's way too late and no amount of planting trees or replacing cows with goats or any of the other relatively easy fixes will solve the problem.

I don't agree. It was equally competent, which is to say, no competence was displayed. But it didn't have the constant cryptocuck and quantumsuck bullshit and they didn't put reich or nazi or their name into the spam filter.

Your understanding of physics is over a century out of date. Get with the times.

Oh look, a denialist that got its feefees hurt. Suck it up, snowflake coward.

I have the karma, you've got a purty mouth

The "editors" have one job, engagement. Slashdot has always been social media, but it wasn't enshittified until B!zX bought it. It was only half-assed.

Even fucking up the summary increased engagement here, as it got you to post, so you're teaching them the wrong lesson.

What I posted is flamebait because it made some manchild uncomfortable about reality.

AGW denialists are the dumbest denialists.

What we should have been doing is supporting nature to help us survive climate change.

At this point we're well and rightly fucked, and we earned it.

We're not doing the things we already know how to do in order to address this situation, which is specifically why we're cooked. We deserve it for watching it happen.

I abandoned Ubuntu and went to Devuan, so I got rid of snap and systemd at the same time. Good riddance to both pieces of garbage.

If you're not confused about what company they're talking about, then what's the problem? A lot of nerds were talking like that back when these products were new. Before it was most commonly written into Micro$oft, people were putting a dollar sign into Compu$erve, to the point where I'd see it written that way more often than not, e.g. on Fidonet threads. Then I got into UUCP (first with UUPC, then Waffle, then SCO UUCP, then AmigaUUCP...) and I would see it written that way on USENET. It's tradition.

There were Unix nerds that looked down on Windows. There were Mac nerds that looked down on Windows. There were Amiga and Atari nerds that looked down on Windows. Back then there were still active VMS nerds who looked down on Windows. And they were all correct, and it's still correct. You can obviously do real work on Windows, but it's not worth the pain. Sadly, it became the de facto standard for working with government, and you needed to run it in order to interface with it as smoothly as possible. Its popularity is like the dollar, it's just too inconvenient to do anything else. Except, "suddenly" (decades of fighting/figuring out how to go around it later) it isn't.

Wine and derivatives run a lot of software very well, but indeed run a minority of it very poorly or not at all. Microsoft and Adobe software are the primary candidates for not running even slightly, and if they do, they definitely do not work right. If you need that software, there is no particular sign that Wine will run it well any time soon, though it will run some of it sort of okay. I've tried quite a bit of it. If you need that software, then you will need Windows, at least in a VM.

Specialized software either works great or fails pathetically with little in between IME. Drivers can be a big problem though, because the software can be looking for the drivers very specifically. If you have Windows software to go with hardware whose interface dongle is not mostly just a ch340 or something, you are probably gonna have a bad time.

Practically everything works great with Linux these days, though. Standards have mostly won and Linux is taken seriously. OSS is now also generally taken seriously and even preferred in solutions large and small. The dependency on closed standards and platforms is waning, and while that's no comfort to anyone forced to run Windows for some compatibility reason now, at least it's becoming less of a problem. Even people who think Windows is fine now recognize that they don't want to be stuck with a dependency on a specific version of it.