Why not both?
There has been some noise about the state of accessibility in Linux last year. Seems that things are improving and the Devs of major DEs are taking things more seriously. From a more recent blog post on the topic:
Developers Are Rising to the Challenge
Here’s the good news: I’ve talked to developers from GNOME, KDE, and Fedora.
They get it. And they’re taking it seriously.
GNOME’s Wayland session is now stable and usable with Orca. KDE is catching up — and has a legally blind developer leading accessibility improvements. COSMIC is building Wayland from scratch with accessibility and global hotkey support in mind. For once, accessibility isn’t just a postscript. It’s in the room where design happens.
This transition is happening — but we’re not being ignored anymore.
The other posts in that series gives a good overview of previous things as well. Seems that author has been successful in raising awareness about the subject which hopefully will help improve things.
You cannot do that analysis with one sample. Why pick one day? That is an arbatary amount? Pick the 1 hour or minute that the CVE was released and you will find rust might be responsible for 100% of CVEs, Take a Week or year and that number drops dramatically. Pick the next day and that drops to 0%. You can select any % you want if you change what time period you are looking at.
The fact that there has been one cve in 5 years of rust in the kernel is a bigger tell. There will be more rust CVEs, and each one is going to be big news as they happen so rarely.
A library cannot add new fundamental things to a language, or, possibly more importantly remove bad ideas from a language.
The article makes a point to say these features are for library writers to help them write simpler APIs for inexperienced users to use. But misses the point of different languages have different footguns that inexperienced users can trip up on.
They really want you to know that HashiCorp, an IBM Company is now owned by IBM. Looks like they have gone over that readme with sed.
Great, now people will read that as 'cold pizza is heathy'. If it makes any difference is will be marginal. Not eating pizza is still vastly more healthy overall. Eat pizza if you want, but don't be fooled to think cold pizza is good for you.
Upgrades is any security or big fix as well. Those tend to be quite safe in point release distros. Upgrading to a new point release version is has all the same problems the rolling release had over the same period all bundle in one messy upgrade (which makes them a huge pain to deal with as they often compound). But between those, the patch upgrades tend to be quite smooth.
I would say the over a longer time period rolling release break in bigger way less often. But they tend to have more but smaller breakages that are easy to trivial to fix.
Less chance of an update breaking things. Lots of small and frequent updates, instead of rare and large update packs/stacks.
I would say a rolling distro update has a higher chance of it breaking something. Each one might bring in a new major version of something that has breaking changes in it. But that breakage is typically easier to fix and less of a problem.
Point release distros tend to bundle up all their breakages between major versions so breaks loads of things at once. And that IMO can be more of a hassle then dealing with them one at a time as they come out.
I tended to find I needed to reinstall point release distros instead of upgrading them as it was less hassle. Which is still more disruptive then fixing small issues over time as the crop up.
It has an LTS kernel. Not a separate version. This does not make everything LTS. This is very different from LTS distros.
It is not just about your pc hardware. I much prefer running the latest software on it as I regularly use features from tools added in the last version of something. I would hate to have to wait 6 months to a year to be able to use new features that make my life easier. That might not be every bit of software I use but enough core things that I would notice.
Email support was the bain of my existence. I forgot how many misconfigured system I came across decades ago that would fill up their filesystem with logs from crons in the root mail dir. Such a stupid default setting. We have vastly better methods for monitoring systems these days then firing off an email when a cron runs.
You can also easily see when the job last ran, if it was successful and when it will next run. As well as just trigger the service if you want it to run now.