There's an explanation somewhere as to why. It has to do with "not breaking" stuff relying on it. So I guess it only answers "why we won't fix it".
Anyway, I don't think this is enough. Or I guess it only works to stop the trigger during install? I have the NO_AUTO_UPDATE set up, and recently needed to update (or upgrade? who knows) a single package and it somehow ended up with Homebrew working for over two hours. I saw it installing python at least two times.
That's not a proper explanation IMO. The thing is - all these settings are introduced "quietly" as new defaults and you have to opt out. So one day you decide to upgrade a package, brew updates itself, and then starts doing all these things that weren't present before (and are most likely not needed at all).
It's very annoying, and a dark pattern to say the least.
And they somehow stack in time. So after a weekend it's popping up over and over until I give up and quit Slack. It's been like this for a year I'd say. There's no way to stop them and they always get focus, which is extremely annoying. How can I revoke this permission from Slack? Seems pretty abusive.
There has been talk about this pretty much since CNNs got good at object recognition ~2012.
But healthcare is a rather conservative industry (for good reason) so it has taken a while to build confidence in the technology and get regulatory approval.
Yeah - I don't recall which company (maybe johnson & johnson) it was but my aunt worked for one that produced a portable machine that used a camera to check moles and used some sort of algorithm to give a predicted score. This was 20ish years ago. I remember she brought it to my grandparents and we had fun checking everyones moles for the day.
Not voting was saying OK to Trump, fully knowing what's coming. This "less than 50%" argument doesn't stand, especially because the winner got proper majority of the casted votes.
especially because the winner got proper majority of the casted votes
This is actually untrue. 2024 was one of those elections where both candidates were so bad, that the winner didn't even need 50% of the cast votes. More and more of those lately, but there it is.
You'll not that Trump and Vance got 49.1% of the popular vote, and Kamala and Walz got 48.3% of the popular vote. They, none of them, could even muster 50%.
We did not decide it. Google decided to kill it. In countries where Opera had major share Google ran aggressive and deceptive (something something faster) campaign with billboards, radio and tv ads. Chrome ads were also everywhere on their homepages (google.com, youtube.com).
But more nefariously, Google kept blocking features and apps based on the UA agent alone. Add lots of tech demos with their custom extensions.
Don't forget bundling Chrome with random apps (I remember cCleaner), making it install silently and automatically set itself as default.
I got caught by this as a kid a few times, I was technical enough to know what was going on, and reliant on a screen reader (which Chrome didn't support back then), so it was definitely a memorable annoyance for me, but I guess quite a few people didn't care.
Vivaldi is roughly 1000 times slower. You need a pretty good computer to run that UI. It also lacks extremely basic features Opera had; like working LRU tab switching. I liked the idea, but it's impossible to recommend.
Is that true? I remember having to change a setting to switch the behavior of tab switching because it was LRU by default and I prefer it in visible order.
It used to work and broke maybe 2 years ago. This tells me that no one is actually using the browser and that no one is really working on it either. It receives chromium updates and then some money-making features here and there.
It's been a while, 8-10 years ago maybe? But quick look now tells me it's still one person effort. That's both awesome and unfortunate. I wish it got more traction back then to attract more active user/dev base.
That’s fair, however the overall gist of the post seems to imply that the numbers data and numbers produced somehow groundbreakingly prove that everyone who has proclaimed it works is wrong and the data and numbers in the post prove that.
Happy to be told I’m wrong, but that’s how I read it.
Very little if anything is ever proven to be absolutely true in all circumstances. The author did a decent job of controlling variables and blinding so their evidence for a lack of effect is substantially more robust than any number of personal anecdotes claiming an effect.
We’ve known for centuries now that people are absolutely terrible at knowing if medical interventions work beyond placebo unless you use rigorous protocols to remove bias and account for reversion to the mean. Yet it seems the message just doesn’t get through to vast swathes of otherwise intelligent people.
Anyway, I don't think this is enough. Or I guess it only works to stop the trigger during install? I have the NO_AUTO_UPDATE set up, and recently needed to update (or upgrade? who knows) a single package and it somehow ended up with Homebrew working for over two hours. I saw it installing python at least two times.
reply