A rising tide raises all boats - if you're going to punish #redhat, make sure you punish all #Linux companies if you can't easily build their entire code tree yourself
If I buy a license of Canonical ESM for Ubuntu Focal how actually realistic is it that in 2030 it will in fact still be safe and secure to use as an internet-connected desktop OS?
Also, what would it cost me for a single license for an individual? I can't seem to find details that actually pertain to my situation
I am genuinely considering doing this but would be remiss if I said part of the reason weren't on principle just to spite #RedHat
A #Canonical employee reported some out-of-tree code broke after something internal was renamed recently in #Linux 5.15.y – and as expected was told this is no regression at all, as the #LinuxKernel does not have a binary kernel interface, nor does it have a stable kernel interface:
Christoph Hellwig in a reply also wrote: "given that Canonical ignores our #kernel licensing rules and tries to get away with it I'm not going to offer any help to Canonical at all."
I've been using #Ubuntu on my main desktop computers since Warty Warthog, and it's mostly been a perfectly fine experience. Some releases were definitely better than others. Like other users I've not always been happy with the choices made and directions taken by #Canonical.
People are starting to offer (and insist) to publish my apps on the Snap Store.
I have decided to refuse. I want to explain why:
Snaps don't appear to get updated. “Publish and forget”.
There is really nothing in it for me except more work.
Every minute spent on Snap is a minute of development lost. I organize events, maintain 10 apps, contribute, mentor students, … on my (unpaid) free time. I really don't have time for this.
This is the most Canonical thing ever. Quick, use our shitty software that doesn't work correctly and locks you into our proprietary platform!!! :blobfoxthinkgoogly:
People who defend snaps kind of baffle me. It's somewhat nice for Ubuntu server applications, but that's about it. The fact that snapd is hard coded to direct to Canonical's proprietary storefront and doesn't support third-party repos should be a complete nonstarter for the format, never mind all the performance issues. This is Linux, why is it okay to have an Apple-style walled garden as your package format of choice? I really don't get it.
I think it’s important to remember that if you’re using the excuse that your software project should not be held to account for being inaccessible because it is released under a free software license what you’re really saying is that disabled people are not welcome in the free software world.
❝Today, thanks to Android and ChromeOS, Linux is an important end-user operating system. But, before Linux, there were important Unix desktops, although most of them never made it. …❞
Haven't Canonical got the message yet that Snaps are very unpopular. This is being forced on users and the people I know—myself included—don't want it.
Is it worth investing time getting into / familiar with an early-stage #Canonical project? Not just for funsies, but with an eye toward production in the target market..
In this one, we have a pretty bad scam app making its way onto the Snap Store, and the steps #Canonical and #Ubuntu will take to avoid this situation in the future, we have the Warp terminal coming to Linux, but still not open source, unfortunately, and we have a proposed API for RGB on Linux, and a lot more stuff, including some good news for Linux gaming:
Hey #Canonical. Stop trying to make everything a #Snap. #Snaps suck. Nobody wants them and we've already moved to #Flatpaks and #AppImages. Stop forcing your agenda on us.
'"Allen Ärgernissen über die noch immer bruchstückhaft wirkenden Umbauten beim Paketmanagement zum Trotz: Ubuntu 24.04 präsentiert sich im Großen und Ganzen als ein durchaus gelungenes Desktop-System. "'
As a proud member of the open source community since 1995, as being part of the OSS revolution as a #RedHat, #Canonical and #SuSE employee, with regrets I have to admit @geerlingguy is not totally wrong: