flatlined

No but you see we at Google aren’t locking down sideloading. It’s the individual app developers. With the api we gave them for that express purpose. Totally not us locking stuff down though, so EU please ignore us trying to indirectly close doors in our walled garden?

Agreed on the former. As for the latter, that’s hard to tell from the outside. No you can’t go back, but if the suffering reliable outweighs the joy, a dignified exit should be supported, and the only one who can really judge that is the one going through it.

If there’s maybe enough to hold on for, try holding on. If there’s a chance for improvement, please try holding on. If there isn’t, then there isn’t.

Either way, I hope for improvement in the future, be it personal or medical. No one deserves this kind of suffering.

Which (pr nightmare aside) I wouldn’t be against. It’s not gonna fly, people are accustomed to ‘free’ browsers to the point they’d balk at the idea. Even if they weren’t most would take a free chromium based browser or Firefox fork over a paid alternative that doesn’t give them anything extra. But browsers are massive pieces of tech, they need a lot of dev time, and the money needs to come from somewhere, just relying on volunteers won’t cut it.

Mozilla has been looking for sources of funding for years, sometimes in ways that are their own type of pr nightmare and sometimes in ways I’m not thrilled by, but I get their predicament. I wish there would be (more) state funding. EU, US. Whatever. Much like governments should invest in public transit we should invest in critical software infra.

I also wish Google’s other branches were divorced from their browser dev branch. The stranglehold on the web given to Google by chrome is a huge part of the problem.

On the one hand that’s supposedly to do with competitive advantage. It makes sense to try to even the playing field, which should have nothing to do with objection on ‘moral’grounds. I’d argue this is mostly a good thing given the iffiness of many groups’ morals.

Case in point, your exact examples, which brings me to the other hand. Banning trans athletes on ‘fairness’ grounds is bullshit. In most sports there’s no known competitive advantage. Where there’s an imbalance they tend to show disadvantage. The rare cases with an advantage for trans athletes tend to disappear the moment you correct for size/weight, which is not something we’d exclude cis athletes for. None of your examples should have happened. They do not hold water on fairness grounds, and any moralistic reasons behind it are reprehensible.

The Dutch translation is great. One of the few books I prefer to read in Dutch over English.

Moers wrote many great books in his Zamonia setting, but bluebear is head and shoulders above the rest.

The books have great art too. Done by the author, as he’s a cartoonist.

It’s a variation on the old saw of “how much is the difference between a million and a billion? About a billion”. Once numbers become so big, it’s hard to grasp the relative sizes. That said, I’m also interested in a more comprehensive breakdown. Seeing who are impacted, how much and where.

What combination would you recommend to replace most common GitHub functionality?