2,413 karma · joined July 3, 2015
1. It's advertised on the two most popular search engines.
2. Microsoft doesn't include Chrome in Windows, but a lot of Windows OEMs pre-install Chrome.
The other half of the reason is that Web applications are way easier to deploy, even if 100% of your users are on Windows, because the second-order-effect of being locked-down is less gatekeeping and less scare screens. If a web app is able to see stuff that it hasn't been explicitly granted access to, that's considered the Browser's fault for allowing it instead of it being the User's fault for installing an untrusted app.
https://analytics.wikimedia.org/dashboards/browsers/#all-sit...
Relevant xkcd: https://xkcd.com/1102/
Because the alternative is that businesses do for data privacy the same thing they already do for things like manufacturing and corporate taxes. That's even worse.
It's a lot easier for big business to control a single state government than all fifty of them.
Of course parties will try to convince people to do that. The question is whether voters will listen.
It's extremely easy to prove to yourself that, if my ranked preferences are O'TruePreference is better than Doe who is better than McBadGuy, then this ballot:
Evil McBadGuy: 0
John Doe 10.0
Andre O'TruePreference 10.0
... is strictly better than this one, regardless of how other people vote: Evil McBadGuy: 0
John Doe 10.0
Andre O'TruePreference 0
> Enough people will do that to obviate the other advantages.I know this happened with Approval Voting, but that doesn't necessarily mean it'll happen to Score Voting. It's likely that voters just didn't read the directions, and thought that if they voted for more than one candidate their ballot would be discarded.
And the HN discussion surrounding it:
https://news.ycombinator.com/item?id=30847133
[Unfortunately, while you can test ranked choice voting systems against each other directly using examples, you can't really test them against cardinal voting systems because the ballots aren't the same. At best, you use statistical models to compare them.]
The scroll bar and find function can be mitigated, but not as elegantly.
The real problem is that, when you load a page in the middle, it’s easy to scroll down, but scrolling UP is glitchy. That one can’t be fixed. https://meta.discourse.org/t/scroll-jank-when-scrolling-up/1...
Interesting corner case where curl seems to disagree with almost everyone else I can think to interrogate.
At least, not without restricting yourself to a tractable subset like dependabot does.
Many computer users run a modified version of a content blocker every day, without realizing it. Through a peculiar turn of events, the version of the content blocker which is widely used today is often called an ad blocker, and many of its users are not aware that it is basically a generic content blocker with a particularly popular block list preloaded.
But CloudFlare doesn’t. That’s why they position themselves as a common carrier.
So it’s fine to call for violence, as long as the violence in question would be legal if it were acted upon?
That makes so much sense, it seems like it would go without saying. If the violent act itself was legal (like a war, or an organized boxing match), why wouldn’t it be legal to solicit or petition for it?
Mostly, they're DOM enhancers, and Firefox has always been coded against its own internally-maintained, enhanced version of the DOM.
That's technically correct, which is the best kind of correct, but horribly misleading.
Firefox has always been mostly written in JavaScript, but not HTML [1]. A bunch of features that are being standardized now, like Web Components [2], are pretty similar to stuff that Firefox has used in non-standard form for decades.
The police aren't going to recommend a ban. They don't want people banned. They want people arrested, tried, and convicted for criminal possession. They're going to recommend keeping the account open until they have enough evidence to take it to court.
I expect that whatever tooling the USPTO uses can probably just ignore those things. They're extracting metadata, not actually rendering it.
2. There should be a webext-exclusive API for placing items above the top layer.