UX is a subjective topic.

Managed devices usually have software installed to track all such “events” that gets periodically uploaded to IT team, or gets automatically flagged to IT team based on security policies of the organization.

If you are using a managed devices, in all likelihood, all of your actions are getting automatically logged/tracked.

Good to know that that practice exists in service based organizations.

Is it a product based or service based company?

In a large organization, IT team/Organization policy will never allow to let you use Linux as your OS unless it is required for project or mandated by client.

With ransomware attacks on ever rise, IT will always try to control all aspects of your office laptop/desktop. As they think they got it sorted for Windows, they will fight tooth and nail if you ever submit it ticket to get your OS replaced with Linux without project requirements.

In my view, as long as I’m allowed to install whatever on my personal devices even while working from home, I’m fine.

Office devices aren’t really my property. For me, Windows during office hours, and Linux thereafter.

https://wiki.debian.org/Microcode#CPU_Microcode

I’m using Voyger iOS client on my phone, so decided to self host the same web app on my homelab.

Split screen mode is useful for me on desktop.

https://github.com/aeharding/voyager?tab=readme-ov-file#self-host

Is it me or this app has issues with smooth scrolling?

This is the most likely reason why all of sudden there is an uptick in attempt to embed malware in AUR build scripts.

But, if you are lazy like me then https://distrosea.com/

Flatpak does have a concept of Verified Publisher. Many distros ship flatpak app store with default filter set to Verified Publisher only.

This can be caused by a faulty RAM. If possible, run memtest from boot screen.

Personally I’m waiting for the day it comes out of “under active development” state so that I can migrate from NextCloud to it.

My bad, I meant “known major issues”. If minor issues are not fixed, they document it on release note. But, at no point any fixed release distro ever released breaking changes “knowingly”.

Are you familiar with the term “Regression testing”?

Bugs are of two types - known (found during testing by Distro maintainer) and unknown.

Fixed release fixes known bugs before pushing packages.

It is following the standard development life cycle.

Wayland or X11?

Just to reiterate the same point - in fixed release, a package version is not released until all known issues are resolved.

At no point, it is end user responsibility to bother checking anything before installing a new version.

taking any action required no matter the os

This is not really true for fixed release distros. I can’t remember when was the last time I had to read through the release note before Ubuntu version upgrade, or upgrading any package.

Rule of Thumb: if your use case is not satisfied by your current Distro, then move to the one that does.

Arch or rolling release distros are great if you want latest version of software/packages as soon as possible. Downside is you need to put more effort/time to maintain it by yourself.

On the other hand, fixed release distros (e.g. Debian) doesn’t offer latest packages immediately. But, given that packages are tested for distro release, so you will have a more stable (in relative term) system for yourself with minimal effort.

I used to like rolling release distros on my college days as I had plenty of time back then. Now, I’m settled on fixed release ditro as it suits my current use case.