DON’T BE FOOLED! This post was made by the cat! It wants narrower TV stands so it can knock them over easier when its owner forgets to feed it!

Exhibit #1 why Hexbear/Lemmygrad are unpopular: this guy

I believe you’ve answered your own question.

Lemmy isn’t Marxist-only. The majority of Lemmy users are what the more vocal Lemmygrad and Hexbear users deride as “libs.” As a thought experiment, imagine that you are one of us for a moment and then browse Local on one of those.

I’m for it, mostly because that’s how I was taught to write in school.

I still maintain my boycott of Amazon over the one-click patent.

It’s a hassle to buy stuff online without using Amazon. The patent expired years ago. Probably no other person is still boycotting them over it (not that it was ever an effective boycott in the first place). But I just can’t bring myself to buy from them.

Writing. Specifically, tech writing. I’ve got an intuitive sense for it, but other than business communication and the occasional bit of internal documentation I don’t have any desire to do it professionally.

I get along great with our tech writer, though, since I’m the only other person at the company who can hold a discussion about the Oxford comma.

Favorite? No idea.

Least favorite? Alan Alda in Canadian Bacon. Dammit man, you were good in MASH, why can’t you act in anything else?

I’ve never talked to an Arch user about Linux, so I dunno how toxic their community is. But I do read Arch documentation, and it’s fantastic. Arch’s documentation has (for me, anyway) taken the place that used to be held by the old HOWTOs back in the early days.

The kind of cooperation required to accomplish this doesn’t speak of a toxic community to me. I didn’t watch the video since I don’t watch YouTube on my phone, but I’m guessing it’s not the Arch community that has issues but annoying teenage “I’m more 1337 than you” jackwads that are the turd in the Linux punchbowl. Those little cretins are drawn to distros like Arch because they like feeling superior to the “normie” users.

I should know, I used to be like that thirty years ago. Most of us grow out of it after we start getting laid.

They wouldn’t be able to build it. It wasn’t until the 16th or 17th century that metallurgy and machining were advanced enough to build atmospheric steam engines, much less high pressure ones.

You need a lot of tech to jump start an industrial revolution.

Native Americans in what would become the US had stone-age tribal societies and oral traditions. It’s difficult to establish a consistent history for groups like that. To make things worse, by the time anyone wanted to make a serious unbiased attempt to document their culture, their culture had been changed long enough that no one alive remembered what pre-contact life was like.

You might have better luck with Central and South American natives. The Aztecs and Mayans had written records, and the Incans left behind cities full of artifacts. Or check out the Inuit - they’re largely isolated so they had less of a change forced on them than the tribes living in more desirable areas.

Or, depending where you are, you could always just seek out the local tribes and visit. Most of them have museums and books written by tribal historians and welcome people with a serious interest.

Install xterm. Bam, you’ve got sixel support.

So it did. That’s interesting.

It was the fact that they used RPMs that made me think they were a Red Hat derivative. I didn’t care for Red Hat (I ran Slackware back then, switching to Debian around Hamm) so I never gave them a chance. Pity.

It never caught on in the states.

IIRC it was originally based on Red Hat (back when Red Hat Linux was a thing), wasn’t it?

I saw that as an adult and it fucked with me.

Everyone is gifted with the ability to control their own fertility. You’re only fertile if you want to be. The only chance for pregnancy to occur is if both partners want it to.

I imagine that would cause a severe population decline, and I’m fine with that. There’s too many humans on this planet already.

Why do I care about the state of the code? It works. Perhaps all these people complaining are really just sick of your proselytization.

To paraphrase Terry Pratchett, “You only get one life. You can pick up five causes on any street corner.”

That’s cool and all, but why would I want to? Display systems are invisible when they work right, and X has worked right for me (save for some pre-EDID config issues) since the 90s. I run a program, it pops up on my screen and I interact with it. That’s all I ask of it.

None of the issues I’ve had with X (drivers, mostly) will be resolved with Wayland. For me, it’s a solution in search of a problem. The only reason I have even a passing interest is that it’s (theoretically) easier to maintain and change as computing changes.

I’ll move to Wayland when I have to, but right now there’s no reason to not use X.

I wasn’t clear. I meant that the issues with X crashing were usually driver issues. I have no idea about Wayland - I don’t use it since it doesn’t do what I want by design.

X does the job well enough to be invisible to most people. Yes, we need a clean start in order to move forward efficiently (lots of assumptions about computer displays from the 80s no longer apply), but it’s good enough for most people’s needs.

Why bother with a display server? Some people - like myself - actually use that functionality. It’s not part of the design for Wayland. Personally, I think that’s a mistake - especially as things become more cloud-based - but I’m obviously in the minority.

Wayland wasn’t the first attempt at replacing X. It has made more traction than any other attempt, though. There’s no real hurry - it’s not like X eats your babies and runs over your dog.

As far as robustness goes, that’s mostly the driver. I’ve yet to see a bulletproof display system, commercial or non-commercial. If you cut out driver issues, X is on par with or more stable than other systems. It had better be, given that it’s had decades of bug fixes with few new features to cause new bugs.

That, and they might be using Object Pascal. I don’t know (I haven’t touched Pascal in thirty years) but I would not be surprised if there’s some overhead there.