Readit News99% of the time I use Chrome it's because some site does not support Firefox (and that often includes Google sites/apps). (The 1% are for APIs that Firefox, consciously or out of resource constraints, does not support.)
In what sense am I "freely installing" Chrome in this situation?
Just today I had a family member reach out to me, unable to use government e-signing on their phone after I'd switched their default browser to Firefox (they were getting tons of ads in mobile Chrome, which does not support plugins and accordingly also no ad blockers). Turns out they support only IE/Edge, Safari, and of course Chrome...
> every device I've ever had Chrome on I've had to seek out and install/make default Chrome
My Pixel came with Chrome preinstalled, as far as I remember. (I don't recall if there was a browser selection screen.)
Sure, that's a Google phone, but then again Windows is a Microsoft operating system.
> the arguments of a closed source subscription service that wants me to switch to the bundled browser of the wealthiest company on earth's most popular consumer OS
Oh, I'd also not advise anyone to switch to Safari. Apple absolutely would pull exactly the same or worse as Google if they could, I have no illusions about that.
I can't wait for the day they're finally forced to actually allow alternative browser engines on iOS and switch to Firefox everywhere.
Do you happen to have any examples? I’m curious to see how broken/what the issues are.
As for getting them out of a jar I really don't know what to say. It's a small jar so use a small spoon? That's what I do, and I presumed everyone else also did.
Your life must be pretty good if getting capers out of a jar is something you have time to trouble yourself thinking of optimising.
Here's something which could be a genuine market mystery (which I know the reason for but it's kind of a fun one to ponder if you don't): Why is the label on angostura bitters always too big for the bottle?
> Well, this website looks like it was designed by someone who learned HTML and CSS yesterday. The floating gradients look like an early 2000's PowerPoint background, and your choice of fonts is more schizophrenic than a cat on catnip. It's as if someone threw up random UI elements and called it an interface. Seriously, who thought that mild, medium, and spicy roast levels were a good idea? It’s a roast, not a taco shop. Even the “See code on Github” button looks like it's desperately trying to escape this hot mess. And the color palette? It's like you asked a five-year-old to pick their favorite colors, then proceeded to spill coffee all over it. The input fields and wait time for your roast are just an added insult to what already feels like digital purgatory. This isn't a roast; it's a cry for a complete overhaul.
I wouldn't be bothered with putting much faith on any of the papers coming out, unless I was a researcher in that space. The dust is far from settled.
I’d honestly rather pay a small one off fee for this same app, without the need for an account.
If you don't agree with the information provided - counter it with what you believe to be more accurate information.
Otherwise? Stop trying to censor shit.