The West forgot how to make things, now it’s forgetting how to code

1) this is an arbitrary bar that needs more qualifiers (all code? All people?) and 2) citation needed.

I don’t care how it was generated. I want you to vet the results at some point with your knowledge and not send me whatever it spits out with no consideration for the results. You’re not sticking it to capitalism when you pass the buck to me. You’re being selfish.

I think we are just too far apart on this to be productive unfortunately. I just urge you to consider the impact of your choices. See my accessibility comment from a different part of the thread:

> I also may be staring at consequences you are not. It’s passing the buck with no regard for who is left to deal with the results at the end.

>What if we are working on, say, accessibility tasks? If I see your work won’t actually help those in society who seriously need these features, what am I supposed to do? My kneejerk is 1) fix it (more work for me, selfish on your part), 2) kick it back to your lazy hands that clearly doesn’t see this as an issue, or 3) send it up the chain (or laterally) where someone else has to ask these questions or - worse - it gets shipped and people who need this stuff are screwed. This is basic ethics.

You need an integral part that knows what the entire chain reaction time is. But if you don't have a buffer, you can't do that part, you can only react strictly to the conditions your suppliers have right now.

A derivative part seems quite useless in a non-coordinated game. But it could in theory pass a "message" upchain that they need to start reacting. Anyway in any real situation it will be easier to pass a message around by telling stuff to people.

At the end of the day, the relative penalty for storage or non-delivery is what will dictate the optimum play style. But it's perfectly viable to use buffers to attenuate the bullwhip instead of making it larger.

I determined that this minimal start was the right confluence of those two preferences with the howto documentation available at the time, so that's what I did.

So I'm going along in rolling releases for years, and even playing games fine (except GTA:V online). Things are fine until there's some weird flickering-window bug that rolls down the pipe and apparently only affects nVidia users who use xfce4. It's an awful and particularly jarring bug.

The workaround is to disable vsync in xfce4, which solves that problem but always causes tearing for me. Even in YouTube videos. (Who knew how reliant we'd become on rote frame synchronization? Why, it seems like just yesterday when I was streaming potato-quality RealVideo episodes of South Park over dialup on a K6-2 box while marveling that any of it worked at all.)

I don't know which party is responsible for that problem, but nVidia has supposedly fixed it on their end in recent weeks. Which is cool, but this distro isn't shipping that version yet. And I'm reluctant to go off-script -- I loathe the idea of letting the nVidia installer do whatever it wants, and I'm not too keen on building my own package for xbps to handle (hopefully with better grace), either.

It was time to fix it anyway.

And I wanted to give Wayland a shot because there's a limitation with SDL that causes the clipboard method used by Factorio to fail to work with large blueprints under X11, so change was already in the air.

And so it began.

KDE Plasma: I couldn't get it to work. With both X11 and Wayland, parts of it would just die without leaving any traces I could find. It was unusable. I spent hours troubleshooting it and only a few minutes of actually using it, which is a terrible ratio. It had to go.

Gnome: It actually worked OK with Wayland. But when I say "worked OK", I mean that it acted like a touchscreen interface -- for toddlers. It didn't crash in mysterious and buried ways, which is good, but it I found it to be an affront to my sensibilities in ways that I simply could not tolerate. I won't apologize for hating it or for feeling insulted by it. That iteration of Gnome is dead to me.

So working down the list of non-ancient desktop environments: Cinnamon? It works. It's alright. It took some kicking to get sound to work because the mixer it comes with makes it impossible to set up default outputs in a way that behaves here and it reverts the system to its own broken ideas every time it runs, but it responded to my kicks without much of a fight and it works. The xfce4 volume mixer is on the taskbar instead, and I removed all traces of the Cinnamon mixer like it was a cancerous tumor, but with that done: Sound works. Regular X stuff works. It's good enough.

I haven't tried it with Wayland yet to see I can work around the SDL+Factorio SNAFU, but it's been behaving itself with X11 for a week or more.

---

Now, that may sound awful. And to be clear, it wasn't fun at all. But at least it's not like my Windows laptop. I've got stories about that, for sure.

One of things that sticks out right now is when that laptop would deplete its battery just sitting in my bag in the car. That was weird, but it became more urgent to fix it when I got the machine out of the bag and it was hot.

The cause for that was an HP printer driver (for a rather old color printer that I don't even own -- I do use it sometimes, but it's 25 miles away) that was periodically waking the machine from hibernation to check that printer's supply status, so it could try to sell me more stuff.

This task was so completely buried in Windows that it took hours to find it, and it was configured by its installer to wake the machine from hibernation -- including, specifically, while on battery. Because that's obviously what every user of any printer needs: Computers that turn themselves on using battery power to sell toner cartridges while hidden unseen inside of a bag in the back of a car.

It didn't have to be that way, but it was this way anyway. I consider that kind of thing to be deliberate in a fashion that extends beyond mere maliciousness: It is instead simply fucking evil.

---

So yeah, Linux is a great desktop.

I'd like to propose a new slogan: "Linux. At least it's not deliberately evil. Usually."

Yes. Part time work.

Google sez: "Total compensation generally exceeds base salary by 30% to 50% for many roles, meaning salary often represents only 60% to 70% of an employee's total worth to the company."

Google sez total compensation includes bonuses, commission, stock options, employer-paid insurance (health, life, disability), retirement contributions, paid time off, tuition reimbursement, student loan assistance, gym memberships, employee discounts, Childcare assistance, commuter benefits, and relocation expenses.

None of those are mandated by law.