Now imagine that knife stabbings became so common that almost everyone started wearing body armor and you start selling body armor defeating knives explicitly. I can honestly see why most people would be upset about that.
In a roughly two-week window of not having adblock enabled, I have seen a ton of "politics-adjacent" ads in Germany. They'd usually start off with something that will get right-wing nuts excited ("This Green Party politician ruined their career, learn more.") and will then pivot to some crypto-scam.
I'm wondering if those will be affected by the new ban as well, or if crypto scams aren't political enough to apply.
1) I'm reasonably confident that this issue is not an accident. Better compatibility / better specs won't help here, I'm afraid.
2) A reference implementation for browser-features is an insanely complex project. Already there are effectively only two entities on the entire planet who can produce a browser that is reasonably close to the current spec. If you forced a reference implementation to exist, it'd probably just end up being Chrome(ium), which is arguably an even worse situation than where we are now.
In most videos, there'll be a whistle-blow that marks the point where the life guard in the video reacts to the drowning person. Upon clicking the right location, you are "graded" based on how quickly relative to the life guard you reacted. You get the "answer" by looking at who is getting rescued.
In my case, it started with a video that appears to be broken (?) the video just ended without any life guard reaction, but you can hit "Play Another Video" which appears afterwards.
I have to admit that those dark patterns on Amazon already saved me a good amount of money. For every order, I have to confirm that I don't want Prime (an estimated) 3 times now. Usually between the second and third click I'm reminded that I should shop around and to look for a better deal elsewhere (and usually there is one).
TikTok and Instagram both limit comments to a single layer of "answering".
I guess that's a "good" alternative if your goal is to prevent the evolution of deep discussion and instead get people to move on and scroll over more ads.
The big issue here (provided that I'm reading the PR correctly) is that it's purely for arrays of the primitive number types. Whereas most real applications (that I've seen) will be sorting objects by some (potentially computed) property, be it an ID, a timestamp or a name. For all of these cases, the linked pull request won't be doing anything useful.
The most useful application for this (outside of getting nicer numbers on a benchmark) that I see is computing the median/quantiles of some property on a bunch of objects that aren't already sorted by the interesting property.
You still see quite a lot of primitive number sorting in library code. If you want your Java code to go fast, you typically stick to primitives in arrays.
Most Java application code doesn't, but it typically uses libraries that do. A sorted array is a priority queue, a binary search tree, etc.
I brew it just like any regular herbal tea and I'm pretty happy with it. The whole ritual with the pipe and gourd is a bonus, but never required.
If you dislike the more bitter flavors about it, try steeping it at a lower temperature (like 70-80C) and only for a short duration (2 or 3 minutes). That should make it a lot more bearable to you. You can also get packages that have less or no stems or powder, which both add to the bitterness.
You're not supposed to brew it like a herbal tea, the proportion of mate to water will be all wrong :) The hotness of the water will also be wrong, mate is brewed with mildly hot water, way less hot than tea.
That said, if you enjoy it, keep doing that way... there's no mate police!
