In the microwave of evil?
pixelscript
If you're not measuring for cooking, why are you measuring? Being that accurate for casual consumption is strange.
Happy Debian daily driver here. I would never ever recommend raw Debian to a garden variety would-be Linux convert.
If you think something like Debian is something a Linux illiterate can just pick up and start using proficiently, you're severely out of touch with how most computer users actually think about their machines. If you even so much as know the name of your file explorer program, you're in a completely different league.
Debian prides itself on being a lean, no bloat, and stable environment made only of truly free software (with the ability to opt-in to nonfree software). To people like us, that's a clean, blank canvas on a rock-solid, reliable foundation that won't enshittify. But to most people, it's an austere, outdated, and unfashionable wasteland full of flaky, ugly tooling.
Debian can be polished to any standard one likes, but you're expected to do it yourself. Most people just aren't in the game to play it like that. Debian saddles questions of choice almost no one is asking, or frankly, even knew was a question that was ask*-able*. Mandatory customizeability is a flaw, not a feature.
I am absolutely team "just steer them to Mint". All the goodness of Debian snuck into their OS like medicine in a kid's dessert, wrapped up in something they might actually find palatable. Debian itself can be saved for when, or shall I say if, the user eventually goes poking under the hood to discover how the machine actually ticks.
The "lonely" part of the name comes from how they're the only player in the industry trying to do what they do.
I have never been in or adjacent to a situation where I had to measure chocolate packaged and sold to be eaten as-is in a recipe by squares broken off of a bar, at the demarcations pre-scored into the bar. If I needed that much control I'd grate it or use a chocolate that came pre-granulated, like baking kisses.
For chocolate bars meant to be eaten, the score lines are very much for sharability first. Any use of them for culinary measurement is at best a peripheral feature.
This probably doesn't hold true for baking chocolate. But Tony's isn't baking chocolate.
Everything works the same, times of website incompatibility are long gone.
Not completely true. It's mostly true. I've daily driven Firefox for years, and the number of websites I've crossed that wouldn't function in it correctly but would work just fine in Chrome was very slim... but not zero. Definitely not comparable to the complete shitshow of the 90's and 00's. That's true. But it's not a completely solved problem.
And with Mozilla's leadership practically looking for footguns to play with combined with the threat of Google's sugar daddy checks drying up soon due to the antitrust suit (how utterly ironic that busting up the monopoly would actually harm the only competition...), that gap can get much worse in very little time if resources to keep full time devs paid disappear.
I recently had a rather baffling experience trying to preemptively avoid this by downloading the stupid app right away, only to discover I needed the website version anyway.
I was attempting to add my Known Traveler Number to an already booked trip with Southwest Airlines, booked by someone else. I was able to link the trip to my account right away in the app, no issue. And I could see the KTN field for my ticket sitting there, empty, greyed-out, and not interactible. I opened up the moble version of their website, completely unsurprised to find it was identical to the app, except for the detail that the KTN field there was functional. Put in the information, changes reflected in the app instantly, and I was in the TAS-pre line that afternoon.
Why did the two versions obviously built from the same codebase have two different sets of capabilities? Why was the website the more capable of the two this time? I have no clue. All I know is I never want to be a developer at a corporation where I'd have to be responsible for this flavor of trash.
The more egalitarian principle would be to not assume. I won't deny that. People from more minority locales have every right to be upset at being marginalized.
But at the same time, whenever I read passive aggressive comments on socials from residents of crown countries or from EAASL people around the world bitching about US defaultism as if people are doing it just to be ignorant dicks, I can only think to myself, "Uhh, hello? What do you think the demographics of this space were? What did you expect?"
Americans are hardly the majority of the world's English speakers, but for all the reasons you listed, they tend to remain a massive plurality, if not an outright overwhelming majority, of any mainstream online English language platform. No, that's not a license to perpetuate US defaultism. But like... read the room, people. Your good fight is far more uphill than you seem to think it is.
I've seen at least one company press kit in rules on how to display their logo refer to it as "respect distance".
For anyone who was using K-9 wondering why Thunderbird looks no different, it's because they aren't different.
They build both apps from the exact same codebase. Only difference between the two are the default color scheme, the branding icons, and the text strings of the application's name. It's literally just a choice of which brand skin you prefer.
Which, honestly, kinda cool. A virtually zero-cost way to keep a few K-9 stans happy.
If adblockers would allow ads that adhere to the acceptable ads criteria, the world would be a better place. Less paywals, less ads and maybe some companies would pay their employees a little bit more.
I disagree. The system may have began in earnest goodwill, but financial incentive inevitably erodes goodwill. ABP becomes incentivized to adapt its definition of "acceptable" based on potential revenues they stand to gain from increasingly persuasive advertisers. Your vision of a better world under this system is at best temporary.
The alternative model, simply paying for goods and services directly, is a far more robust solution.
I don't think the existence of large instances is in itself strictly antithetical to decentralization. The network effect makes them inevitable.
The power in the fediverse is everyone has a standard toolset to interact with the entire fediverse. Most people won't, and that's okay. The important thing is that, should larger communities become too oppresive as they gentrify, replacing them is a cheap decision, as you and everyone like-minded with you can squad up and leave at any time and lose nothing as the standard tooling of the platform facilitates that migration. You have mobility in the fediverse, and that permits choice to those who seek it.
This will stop being true once the larger instances start augmenting their experiences with proprietary nonsense. Features that only work there, that you can invest into and become dependant on, that you'd have to give up if you leave.
The day that happens will be the day that chunk of the Fediverse dies. Or, well, it won't die, it will probably flourish and do very well. But it won't be the Fediverse anymore. It will just be another knee-high-fence-gated community, that happens to run on Fediverse tech.