In my experience rear-mounted sensors are the most accurate, closely followed by under-screen sensors. Side-mounted sensors are utter garbage.

Accuracy isn’t even that much of an issue, it’s that the side-mounted ones are far too easy to accidentally trigger just by handling the phone. I can’t count the number of times my last two phones told me I had three incorrect fingerprint attempts after I had just pulled them out of my pocket.

Then I got a Pixel and I have no more such issues and virtually perfect accuracy. Same on a Samsung tablet. Same on an old phone I had where the power button was on the rear and had a full-size sensor.

Basically, I’m perfectly happy with any front- or rear-mounted full-size sensor. Those tiny side-mounted ones suck.

It happens on Linux – after your package manager has updated Firefox. Which typically means that you told it to. So it’s not really a surprise.

Oh, right. Fast Boot. I forgot about that bundle of joy.

But that’s wasn’t the only instance of an NTFS volume suddenly being broken. Another favorite was when I shrunk a volume on one disk from Linux (and then remembered that Windows correspond done it better) and rebooted to have it fixed and Windows proceeded to repair one on a different disk.

NTFS feels rock solid if you use only Windows and extremely janky if you dual-boot. Linux currently can’t really fix NTFS volumes and thus won’t mount them if they’re inconsistent.

As it happens, they’re inconsistent all the time. I’ve had an NTFS volume become dirty after booting into Windows and then shutting down. Not a problem for Windows but Linux wouldn’t touch the volume until I’d booted into Windows at least once.

I finally decided to use a storage upgrade to move most drives to Btrfs save for the Windows system volume and a shared data partition that’s now on ExFAT because it’s good enough for it.

I gotta be honest, I haven’t used a dedicated sound card since the Vista/7 era when EAX stopped being a thing and onboard sound could handle 5.1 output just fine. The last one I had was a SoundBlaster Audigy.

These days the main uses for dedicated sound interfaces are for when you need something like XLR in/out and then you’ll probably go with something USB.

Port 220.

IRQ 5, port 220h, DMA 1 was what I used for my SoundBlaster 2.

Later I used IRQ 5, port 220h, DMA 1, high DMA 5 for my SoundBlaster 16.

Mind you, the real winner is of course Android. It has a consistent, easy to learn interface and a wide range of applications that integrate nicely.

And we don’t need to speculate; it has already won and is the true face of Linux for the masses. Plenty of young people don’t even own traditional computers anymore and do everything on their smartphone or tablets.

And that’s why this entire discussion is really just a form of fan wank; we don’t need to find a unified UI for Linux because it has already been found and has a massive market share. You may not like it but this is what peak performance looks like.

Everything else can be as complicated, janky, or exotic as it wants because it doesn’t matter.

Honestly, if you want one simple DE for everyone it should probably be XFCE. Dead simple to use, feels vaguely familiar to Windows users, not overly complicated.

KDE is heavily customizable, Gnome is very opinionated, and tiling WMs don’t adhere to orthodox UI patterns. Those are all suboptimal if you want something usable by the absolute widest range of users.

Gtk and QT weren’t consistent but there was a Gtk style that used QT as a rendering backend, which allowed you to get some semblance of consistency. Then they came up with Adwaita, which doesn’t really allow that anymore.

To be honest, I’m kind of afraid that Linux will go the day of Windows with zero UI consistency because of apps that can’t be themed to even look vaguely similar or may even take over the window decorations.

I kinda liked it more when gtk-qt was still a thing and you could actually get a semi-unified look for the while environment.

Probably smug about how her theme started playing in my head as soon as I saw the picture.

Even if you assume that the software you run will never have exploitable security issues, AV can also keep you from spreading infected files e.g. through forwarded mails.

Counterpoint: The rest of the Fediverse can see it too so it’s not just for Lemmy.

Windows Phone was mostly sabotaged by first-party developers. Microsoft has a history of abandoning their mobile phone OSes after very short periods of time and nobody trusted them not to do it again. As a result few app developers bought into the ecosystem and smartphone enthusiasts told their friends not to get Windows phones, causing modest sales, causing Microsoft to immediately drop the platform.

As everyone expected them to.