So they've upgraded to 7.2, which is EOL as of a week ago. And not even the latest 7.2 version, they ship .11 when .15 is the latest.

My opinion of VanillaOS + a dev response to it: https://discuss.tchncs.de/post/66437447/27748310

In another comment, I posted a link to the CRAM presentation that mentioned a chip.

This article also mentions some hardware:

Because CRAM is stored in RAM and treated as RAM, with full cacheline/byte access, it can be accessed in a read-only fashion with little delay; just the cost of hardware-offloaded compression.

I don't think it would say that if they meant the CPU was doing the compression.

It's not using the same hardware, this seems to use a special compression chip.

To me this feels more like the benefits of a CPU or GPU upgrade. Things run faster, but not due to software improvements. When people talk about things getting optimized due to the high RAM prices, I think most people are referring to software improvements.

Does it count as optimization? For supported hardware, it's certainly cool. But it's not making inefficient software better, it's making better use of the hardware.

A package, meant to run anywhere and be sandboxed.

However, they are only properly sandboxed on Ubuntu. They have some downstream AppArmor patches that haven’t all been accepted. They’re decently sandboxed on other AppArmor distros. Basically no sandboxing on distros that don’t use AppArmor, like Fedora.

You have to be careful with in-house developed tools though. Canonical outright owns the majority of the code and outside contributors need to sign a contributor's licensing agreement that would allow Canonical to use their code in a proprietary version if Canonical chose to do so.

Yes, the GPL version would still exist, but Canonical could continue working on the proprietary version and not push the commits to the GPL version.

I'm not saying Canonical would do this. And you can replace "Canonical" in the prior sentences with any company and/or software that requires a contributor licensing agreement.

I'm not a believer in the theory that Canonical is trying to migrate everything to MIT so they can have their proprietary Linux. Some people think that their move to Rust projects is a cover for that goal.

But in this case, Canonical Sequoia PGP is still GPL, so the conspiracy doesn't make sense here. Hence my joke.

All evidence just points to Jon Seager, VP of Engineering at Canonical, just really liking Rust.

Surprisingly, it’s LGPL v2.

It's almost like Jon Seager just really likes Rust.

I find it highly concerning that Ubuntu is using Rust as a guise to replace GPL components like GNU GPG with GPL components like Sequoia PGP.

/s

It can get run automatically by things like Gnome Software.

The vast majroity of tasks work without issue. But there's a lot of edge cases where uutil fails. When those are found, new tests are added to track them and prevent future regressions.

And new test cases are constantly being added. And with those new cases, the pass rate drops.