Apple have always preferred preserving letter forms over hinting, so Macs are therefore also "blurry" on lower DPI displays. The reason they aren't these days is because the DPI is higher.
Usually when people complain about this, the comparison is to Windows, which prefers strong hinting, i.e. snapping the font shapes to within (sub)pixel boundaries.
There also used to be patent encumbrance issues around subpixel rendering, making Linux font rendering on TFTs overall worse by default, but as of 2019 those have expired. Some distributions had already enabled those features anyway.
With any reasonable resolution screen (1080p or more), you can have both good preservation of letter forms and a non-blurry image, simply by applying a sharpening filter after antialiasing. Some image downsampling methods, such as Lanczos filtering, effectively do this for you. The tradeoff is one can detect some very fine 'ringing' artifacts around the sharpened transitions, but these don't impact readability in any way.
I guess in the same sense that every functional aircraft is. Taking everything apart and putting it back together, replacing worn out parts, is considered normal maintenance.
After breaking my Google Assistant with a custom ROM, I unintentionally found out that yes, there is a setting for the default assistant app in the settings. I don't know if any actual alternatives exist, but you can definitely change the default settings. My issue was that Google Assistant didn't realise that it was set as the default, and my attempts to launch it just brought up a prompt to configure it as the default assistant.
The Pixel launcher is deeply integrated with Google, so that doesn't support switching search providers I think. You can install any other launcher you want if you dislike searching through Google from the home screen.
The expert opinions that I've seen so far have indicated that geoengineering at any scale that we're realistically able to produce on a short notice is unlikely to have a sufficient effect on climate change. Essentially it's a pipe dream at best, and a way to create additional (localised) disasters at worst.
If the only proper argument for doing it is that "the left" is against it and "the right" is for it, that seems comparatively weak.
That sounds like a critique far more applicable to non-experts arguing that there's no need for any kind of modification to our consumption patterns or energy use, because if "the left" really cared about the environment they'd just set off our nukes or radically change the composition of our oceans instead
It would be strange, if this were truly an emergency, for people who believed it to be an emergency of the highest degree...
To whine and screech "that's too dangerous, don't do that" when other people were proposing solutions. These are the same people who are touted as the experts, mind you. This means that when journalists and talking heads and other jackasses say "but the experts don't even think those things will work", they are talking about the same people who claim that there is an emergency in the first place.
They aren't interested in potential solutions. It's just an attempt to wrestle political power away from those who currently have it and implement economy-murdering policy because they're mad poor people eat meat.
Well, ok, but since the tools and libraries don’t exist yet… Instead of waiting for somebody else to build middleware and hope it will be good, what would it look like today to design and implement an app that works on both visionOS and OpenXR?
That’s a question that I find interesting. Even if I don’t end up building such an app, it would illuminate the differences between Apple’s SDK and the rest of the industry.
Morally, it's pretty significant that we make conscious decisions (as a process that we often see as distinct from the rest of the animal kingdom) to kill and eat thousands of other animals mostly for the sake of taste, rather than for the sake of necessity, which is why most other animals hunt.
Used to be that way for me too, but I believe with the latest LTS the slowdowns just went away. I'm using Firefox through the default Snap packaging every day, and it's just fine.
This is also with the distro installed with all default choices. If memory serves me right, using btrfs for one can result in any number of weird performance issues.
I thought it was fine too until reading this thread. and I tried opening some cpu intensive pages in the snap version and in a standalone version. the Snap version makes my cpu max out at 100% and i get soft frozen out of my desktop, the standalone never went above 80% .. Now we can blame the pages for being shit in the first place but, I dont want to have to restart because I opened the wrong page.
As far as I know, Servo wasn't ever really intended to be a production browser. But significant parts of Firefox have been rewritten in Rust since, and those parts have included bits from Servo.
Usually when people complain about this, the comparison is to Windows, which prefers strong hinting, i.e. snapping the font shapes to within (sub)pixel boundaries.
There also used to be patent encumbrance issues around subpixel rendering, making Linux font rendering on TFTs overall worse by default, but as of 2019 those have expired. Some distributions had already enabled those features anyway.