Would to see them publish stable releases via this apt repository as well.
Not a fan of the XPS line (expensive, not great thermals, and meh port selection) and I have never own one (though I've seen others with them). That said, I have a few of their Latitudes (currently using Latitude 7420) and one Precision and those run Linux really well.
One thing most people don't realize is that Dell does support Linux (ie. Ubuntu) beyond the XPS line and you can buy Latitudes or Precisions with Linux support OOTB. Additionally, Dell ships firmware updates via LVFS on their XPS, Latitude, and Precision lines. The support isn't perfect, but I have been happy with using Dell hardware and Linux for over a decade now.
PS. You can get really good deals via the Dell Outlet (my current laptop is refurbished from there), and you can usually find a number of off-lease or 2nd systems or parts on Ebay (very similar to Thinkpads).
No word on how long it will get software support though. With everyone else going to 5 or 7 years of updates, Motorola's typical 2 year support cycle is a huge negative.
FYI, Ubuntu/Pop!_OS have already pushed out updates.
I wish they had a mastodon account... they have https://mozilla.social, but they don't have an account there... which is bizarre.
They do have an account for Firefox Nightly and Firefox Dev Tools account though.
I think this is the author being humble. jmmv is a long time NetBSD and FreeBSD contributor (tmpfs, ATF, pkg_comp), has worked as a SRE at Google, and has been a developer on projects such as Bazel (build infrastructure). They probably know a thing or two about performance.
Regarding the overall point of the blog, I agree with jmmv. Big O is a measure of efficiency at scale, not a measure of performance.
As someone who teaches Data Structures and Systems Programming courses, I demonstrate this to students early on by showing them multiple solutions to a problem such as how to detect duplicates in a stream of input. After analyzing the time and space complexities of the different solutions, we run it the programs and measure the time. It turns out that the O(nlogn) version using sorting can beat out the O(n) version due to cache locality and how memory actually works.
Big O is a useful tool, but it doesn't directly translate to performance. Understanding how systems work is a lot more useful and important if you really care about optimization and performance.
Headline is a bit misleading... This is just Tails updating to the latest LTS kernel, which has the security fix (which many other distributions have done).
This update is a good thing, but the headline made it sound like the Tails project was contributing a fix to the kernel.
Anyway, thanks for sharing.
Currently self-hosting my own mastodon server and honestly the setup wasn't too bad (using docker)... much more straight-forward than I feared.
My main concerns, which Julia mentions, is that if you have a small instance, you are very much an island as the way federation work is not what you expect. For instance, as Julia notes, if you view a new person's profile on your own instance, it will look empty (as if they haven't posted anything). Lemmy also has this issue if you view a community you have not subscribed to yet for the first time.
Likewise, my "#explore" tab is basically always empty and discovering new tags or people is difficult if you are just looking on your own instance (I basically have to go to Fossotodon or another instance to find new things and then import them into my own instance). I've recently learned that you have to have a third party application basically seed your instance with posts... again, similar to the bot tricks use for seeding Lemmy with communities.
Overall, I think discovery is a big pain point for the fediverse and ActivityPub. It's great that we can have our own instances and control our own small communities, but it seems that we are lacking the ability to really connect across instances and form experiences that really bridge across multiple communities.
As a parent... I feel this. Well, I remember feeling this. My small beings are a bit larger now and more autonomous :]
Still exhausted though. :|
I wonder if it is because of the various outages on both instance and the new "dead instance" detection, lemmy.ml has temporarily stopped receiving updates?
The federation code now includes a check for dead instances which is used when sending activities. This helps to reduce the amount of outgoing POST requests, and also reduce server load.
According to Debian Releases
Debian announces its new stable release on a regular basis. Users can expect 3 years of full support for each release and 2 years of extra LTS support.
So about 5 years, though it is not clear how well this works in practice (how much is actually updated and how well supported).
From the Debian Wiki - LTS:
Companies using Debian who benefit from this project are encouraged to either help directly or contribute financially. The number of properly supported packages depends directly on the level of support that the LTS team receives.
I think this is sort of what the article is pointing towards... long-term support really depends on commercial support, as volunteers are more likely to work on the current or more recent thing than go back and backport or update older things. If corporate funding dries up (which it appears to be doing), then while volunteers will still contribute some to long-term linux distributions, it won't be at the same level it currently is with commercial support.
Really detailed and cool response from the kernel developer. I also found the use of the recent BPF feature to provide a workaround until a proper kernel fix lands really interesting.