mastodon 4.7.3🇵🇷 cncf.io/developer-relations:community
Formely: #VMware • #Heptio • #Canonical • #Ubuntu • #Kubernetes • #cloudcustodian • CNCF Ambassador Emeritus
11th ACR Vet • MSU #Spartan • Beagle Lover
he/him
I love: #metallica #megadeth #ghost #rush #tool and all sorts of #metal with a side of #aliceinchains and #faithnomore - then chilling with #pinkfloyd
Tech: 
and Flathub!
Digital Sovereignty isn't just for nations!
Now that the desktop has reached The Final Shape we turn attention to our homelabs.
Been making great progress on this, we're at v .8. This one is boring. Knuckle just installs flatcar.
But we want cloud native magic so we're building "Bluefin Server" but not sure on the name. And it'll run flatcar, and in there your magical bootc factory runs and your bluebuild just worked ootb. And the Fedora one will come with coreOS, tekton, forgejo, konflux, etc.
A place for both - if we design the homeserver and desktop as one unified WHOLE, we could do a ton more stuff. The tech is already finished.
A little surprise for ya'll today.
https://docs.projectbluefin.io/blog/the-dinosaur-and-the-hummingbird/
Smart move by Canonical. They've got an entire development platform and store to distribute it with.
And I'm sure they'll be more than happy to take agent assisted Flutter code into their store.
Getting there #gnome ...
If my job was to distribute software and after thirty years all I have is 4% success rate you would fire me.
It's long past due to let the experts who make the software ship the stuff.
Everyone else in #linux has figured this out except the Linux desktop.
"Sir the #linux users are rioting again, they hate electron and want a native app."
"The people that always cost us money? Fine, I guess I'd rather just shut them up, what platform stack to they want?"
"Oh they purposely don't have one. They're quite proud of that apparently."
"What's for lunch?"
What happens when you spend 30 years telling app developers that they suck at distribution and packaging?
They bail. Oh, and a 4% market share.
I don't wanna scare any app developers from publishing on #linux of course.
The way it works is they'll ship a 5 year old version of the thing and then tell the users that breaking your software is a refined skill.
You probably don't want to look to see how much money some orgs are purposely siphoning away from application developers.
Check it out man. Millions of application developers in the world. Millions.
They can easily publish on any platform except the #linux desktop.
Yeah the way it works is only a handful of people know this super complicated process of uncompressing a tarball from a web server and splatting it on a disk. No you can't do it yourself you have to get permission.
You will choose to do it yourself. If you love enshittification do we have a model for you, the users give you root to their computers!
What do we do with all our bugs? We promised people we're good at this but ends up some dude named Sisyphus already figured it out.
There's a poster at the entrance of this coal mine of toil that says: "We add value."
I totally believe that!
@levitating@mastodon.sdf.org @corbet@social.kernel.org @zonker I'm thinking more for the "I don't have time for this just get me to the article. Quick thought to put on the subscription link:
Welcome to LWN.
You've reached a page that is for subscribers. Our content is free for the community but in order to provide the best in Linux coverage we need [to be sustainable](subscription link).
One of our existing subscribers was kind enough to send you this free link. Tips always appreciated:
[ I want this article now, PAY YOU BUTTON ]
This isn't just a site about Linux News, LWN has been covering Linux since the beginning. Here's a sample of some of our best free content:
And not only do we offer the most indepth coverage of Linux and its ecosystem. We participate in the community. When you support LWN you help us support the maintainers who bring you Linux.
[ BIG PAYME BUTTON ] <-- One click to send you money.
Thanks for the one time donation, [subscription offers]:
... and so on.
In kubernetes someone named "The Harbringer of Deprecation" keeps the ecosystem healthy.
If you stay on a deprecated piece of kit like nginx-ingress it's on YOU to pay for the fork, spend super expensive developer time, or pay an organization to sell your tech debt back to you. (As a service!) We spend an inordinate amount of time educating users on the importance of keeping their platforms up to date - you have no choice at this scale. And even with this known policy the stress on our OSS maintainers to deal with this crap is unacceptable.
Imagine instead if kubernetes never developed Gateway API because people are just fine with the status quo and THOSE people made the decisions.
