1,852 karma · joined October 25, 2020
Look at it this way though, this site is low-key a CV portfolio piece because he isn't just writing about dithering, he's demonstrating that he can research, analyze and then both code and create a site at a level most vibers cannot.
I keep both for naming compatibility and also because the 1.0 Liberation versions had truetype hinting (2.0 and up did not).
Calibri is a high-quality font that works as body text, but it's cold.
Times NR on paper is fine, on screen it is not fine unless you have a high resolution display.
h264 is a very good codec.
And not even the nice Cerveza Cristal kind of ads.
The old light regulation actually had a limit on how bright the running lights could be.
The new LED light regulation says you can have it as bright as the manufacturer wants it to be.
So now there is the problem of misaligned headlights that don't point at the road but instead point at cars, and are as bright or brighter than the old incandescent high beams.
I have to have my rear-view mirror permanently flipped at night now. I never needed to do that in the past except when some idiot actually was using their high beams.
I believe flashing lights are actually less safe as it encourages the driver to look AWAY from you. I certainly don't keep staring at a flashing light.
The radio sounds much like Intel's ME.
I think we all know there's a problem, but we don't have the power to do anything about it because what alternative is there? Ancient hardware?
I have three observations to make.
1) There is a pain point in KDE involving windows on top of another fullscreen window. Specifically, the Live Captions app. This is a design problem that other OSes like Microsoft Windows doesn't suffer from. What happens is, if you leave the taskbar in place and want to have the captioner running over video and make the video fullscreen, you can't with KDE. I eventually figured out a hacky workaround in that if I turn auto-hide on for the taskbar, I can then alt-tab the Window and it'll stay on top. I did see some talk about this window behaviour. It's nuts that an accessibility feature needs the user to make the taskbar auto-hide first before it works. It would be nice if there could be a setting where it is "this window is on top of everything".
2) SteamOS as having a large device-specific installed base, I think there is value in the KDE team encouraging Valve to turn KDE from a snapshot to a rolling release as Fedora has done where KDE is rolling but the rest of the distro is a snapshot. Why this matters, is because when it comes to bug reports and the like, the KDE bot basically closes them because Valve's KDE is "unsupported" because they only seem to rebase once a year or two. I know they did move to 6.2 with 3.7, but I found 3.7 buggy and thought KDE looked worse and had worse scrolling performance (maybe setting conflicts from the 5.27 version?) so I just switched back to the 3.6 version with 5.27 where everything looks right and scrolling moved smoothly. I know they changed the kwin compositor a lot in the 6.x series, and I suspect there are regressions in it, so if it isn't rolling, people are stuck with a buggy compositor? That sucks.
3) Setting upgrades.. so with SteamOS, Valve was shipping the 5.2x series of KDE. Now 6.2, and the next rebase is probably going to be 6.x on Wayland instead of X11. So there's a lot of legacy cruft settings that carry on and I think they cause glitches. I always used to do clean install of Windows versions, and think it would be nice to be able to do that in KDE, but there's a lot of legacy cruft with various settings and conf files scattered in various random folders. At some point it really should be cleaned up.. one central folder for all settings.. no some settings are stored in a KDE4 folder, and others are stored in this other one KDE5 introduced, etc.
This is the weakness of cloud services.
My suggestion is, install Microsoft Security Essentials (you can get a copy of the installer out of archive.org) and definition files are still published for it and are up-to-date. MSE is what became Defender in 10. The Defender in 7 is not the same and doesn't scan for the same things. MSE is needed to replace it.
Might still be worth taking a look at as an experiment since this codec separates text, background and images into different layers, even when converted from another format.
Arch-capitalists push for these things in order to reduce cost as much as they can without consideration for society's future or well-being. E.g. laying off American workers in order to hire H-1B workers from corrupt countries where many lie about their experience and/or forge credentials. We have all seen how everything is getting worse in multiple countries now because of corporate control of society.
I do not for a second believe that they actually will implement UBI. There will be conditions attached to it. I don't know what the conditions are imagined to be, but it won't be as simple as these breathless articles about UBI make it sound.
Meanwhile, all these arch-capitalists are building their private doomsday bunkers underground.
Why are they building bunkers underground if everything is fine?
So, given that this will happen everywhere, does it really make a difference what MS does?
v40 with slight hinting and greyscale or subpixel works, but I don't tend to use the fonts that are meant to be used with slight hinting and later fonts can't handle anti-aliasing off at all.
You can easily do this on a per-app basis with flatpaks.. you can set an environment variable with flatseal, and you can drop a fontconfig folder with a custom fonts.conf in the flatpak's var directory.
I like that it quarantines most of Facebook's shenanigans with cookies and the like.
I can't compare Brave's adblock to uBlock Origin, but it's probably good enough.