One thing that stuck out to me about this is that there have only been 32 years since 1993. That is, if it's happened 6 times, this threshold is breached roughly once every five years. Doesn't sound that historic put that way.
Yes, but Orion uses WebKit intentionally on desktop as well, unlike Chrome or Firefox which use their own engines on desktop but WebKit on iOS, so it's a bit different in this case.
If we assume this means "in the next 50 years", they wouldn't be totally wrong. You could make the case airplanes were only on the cusp of being "a meaning[ful] part of life in America" by 1953 – planes only overtook trains for domestic US travel in 1955, and 1957 for trans-Atlantic.
I don't think any of that means the benchmarks shouldn't be taken seriously. GP didn't say they expect Bcachefs to perform like EXT4/XFS, they said they expected more like Btrfs or ZFS, to which it has more similar features.
On the the configuration stuff, these benchmarks intentionally only ever use the default configuration – they're not interested in the limits of what's possible with the filesystems, just what they do "out of the box", since that's what the overwhelming majority of users will experience.
By the way, it looks like the MermaidJS implementation of the WiiU example is broken due to subgraphs not creating namespaces. That is, the `rom` node in the `amd` subgraph is overwriting the one in the `ibm` subgraph.
I'm just getting "invalid response." in a 500 response from the `anubis/api/pass-challenge` endpoint – weirdly, when I added breakpoints and stepped through the code myself, it worked, but if I load again, I get the error. Maybe there's a timing component? (Firefox stable)
You might be surprised at the CPU usage of rendering a GIF. I'm not sure why, but I've previously noticed Slack takes noticeably more CPU when there's an animated emoji on screen.
Apple Music's library features much more closely mirror the iTunes style, i.e. you have a library you can browse outside of just the "liked songs" pseudo-playlist. For instance, in Spotify (AFAICT) there's no way to browse all the songs in your library by artist; you can only list the artists you've followed, which is unrelated to whose songs you've liked, and go to their general artist page.
Personally, this is the top contender for a reason for me to switch away from Spotify.
The "press again to fall back to the browser's key binding" solution many sites use for ^F isn't perfect, and won't work for all scenarios, but it definitely helps.
This article mentions a notable limitation of the HSL colour model:
> Perceived brightness is not at all uniform at equal starting points, it depends on the hue, as well as the saturation.
…but it doesn't mention an (under-discussed) solution available: using a better colour model. OKLCH uses similarly understandable coordinates, "chroma" being roughly the same concept as "saturation", but is designed to avoid just this kind of problem. That is, if you change the "hue" coordinate, you can reasonably expect the perceived lightness and chroma of the resulting colour not to change. Where such a colour does not exist, e.g. a blue with the same lightness and chroma as #FFFF00 yellow, it's simply out of gamut.
There's a colour picker web app[0] that shows the boundaries of the space along with smaller spaces like sRGB, and it's helpful for getting a feel for it. It also links to a post[1] laying out the reasons to use OKLCH in web projects (it's now supported by all three major engines), and the post[2] introducing OKLAB (same space, different coordinate system) is heavy on technical details.
I think your point is that bad PR affects your decision not to use Intuit's products, but I'd argue they're a perfect example of bad PR not being a problem. They have sensationally bad PR, yet they're worth >$100B, one of the 100 most valuable companies in the world, and they dominate their category.
I know that OsmAnd has fairly granular routing preferences, including a "preferred terrain" setting with "hilly", "less hilly", and "flat" options (as well as a "use elevation data" option which I don't quite understand).