As an internal implementation detail, it’s fine and pretty standard. Exposing it to the end user so that they have to know whatever janky-ass domain and capitalization you picked to run your application is braindead.

Exactly. Everyone complains about ad tech and enshittification until you point them to the conveniently located button that lets them pay for the service…

It’s just Maslow’s Hierarchy. The person who doesn’t have a job should be egocentric, at least in this narrow area of focus. If your position is that people should prioritize abstract societal benefits over their own security and well-being, I’m not sure what to tell you other than to prepare for a life of people disappointing you.

Many of the people who currently experience the privilege will be pissed off and view it as unfair. But in reality they’re getting a taste of what other minorities already experience.

There are two competing lenses we can view this kind of thing through, and both are valid. First, there’s the macro lens in which groups like women are significantly underrepresented, and most reasonable people believe that to be a problem we’ve created that we need to solve. It’s not that women are bad at this job. It’s that women have been pushed not to participate for reasons we think are bad. Through that lens, an obvious solution is to bias things in favor of women for some period of time to get to a steady state where the system won’t automatically fall back into gender-bias as soon as we take our thumb off the scale. That’s a reasonable theory, and pursuing it does a lot of good.

But there’s a second lens in which individual people with names are trying to participate in the labor market. The fact that men have had a built-in advantage does not imply that any man looking for a job would only be able to get one by leveraging an unfair advantage. If we think talent and hard work are equally distributed through the population, then temporarily biasing things away from men is, to the man currently trying to find a job, exactly as discriminatory as anything that prior generations have faced. The fact that there’s a societal good being pursued doesn’t make that harm go away either. It is unfair, and we should recognize that. We may decide we have to do it anyway, but I’m not a fan of the idea that “let’s mistreat them like other people were mistreated” is inherently a good thing.

I accept that I’m in the minority on these things, but I value simplicity really highly, and I mean “simple” as a very specific concept that’s different from “easy”. It can be harder to resolve library dependencies on a system where everything is installed using the native package manager and common file systems, but nothing is as “simple” as ELF binaries linking to .so files. Nested directories branching off of / is “simpler” than containers.

Do I have any practical reason for preferring things this way? Not really. There are some ancillary benefits that come from the fact that I’m old and I already know how to do more or less anything I need to do on a Unix system, and if you tell me I need to use flatseal or whatever, I’d rather just use users and groups and tools that have been fine for me for 25 years. But that’s not really why I like things this way. I have no issue with embracing change when it otherwise appeals to me --I happily try new languages and tools and technology stacks all the time. What it really is is that it appeals to the part of my brain that just wants to have a nice orderly universe that fits into a smaller set of conceptual boxes. I have a conceptual box for how my OS runs software, and filling that box with lots of other smaller little different boxes for flatpack and pyenv and whatever feels worse to me.

If they solved practical problems that I needed help solving, that would be fine. I have no problem adopting something new that improves my life and then complaining about all the ways I wish they’d done it better. But this just isn’t really a problem I have ever really needed much help with. I’ve used many Unix systems and Linux distributions as my full-time daily use systems since about 1998, and I’ve never really had to spend much effort on dependency resolution. I’ve never been hacked because I gave some software permissions it wouldn’t have had in a sandbox. I don’t think those problems aren’t real, and if solving them for other people is a positive, then go nuts. I’m just saying that for me, they’re not upsides I really want to pay anything for, and the complexity costs are higher than whatever that threshold is for me.