Your decision to use Free/Open Source software doesn’t give you any moral superiority over others who make different choices.
Conversely, you have no right to feel attacked when circumstances require you to use closed software.
The real world is not for idealolgical hardliners
@ValknutDoc@chaz_6 No community includes everyone
“a group of people living in the same place or having a particular characteristic in common”
Anyone who doesn’t share that characteristic is by definition not part of a community
Folk really have warped perspectives and expectations in this area
The whole “Rust in the Linux kernel” drama should be a lesson to all in Open Source
The technology doesn’t matter
Working with other people does
Doesn’t matter if Rust is a gift from God, God doesn’t control what gets in the Kernel, maintainers do
Technical arguments are moot
@ValknutDoc@chaz_6 I think it’s often overlooked how the “community of maintainers” may have needs & interests that differ from the “community of users”
And given the former is doing the work, often their needs do, and probably should, trump the latter
FOSD doesn’t mean users get to rule devs
Hi! In case you missed, my #FOSDEM talk about creating a #rootless#container manager from scratch is available!
We'll talk about the basic principles to build your own container manager, using #lilipod as an example:
https://t.co/oatxs0hjjc
#opensource#linux#distrobox
@BrodieOnLinux Perhaps that’s a good argument for not rushing to adopt everything R4L throw around then, is it.
Stuff in the kernel has a typical lifespan of decades
No maintainer should be comfortable accepting ANYTHING from R4L until there is a reasonable expectation it might last a while
@DaveAirlie@BrodieOnLinux Exactly - Linus is a federated/feudal project; Maintainers are Lords of their own domain and Rust4Linux need to accept that not all maintainers want, or can, accept their code
It’s a long road, and Rusters can’t quit at the first hurdle. There will be more
@BrodieOnLinux While I appreciate your intent to protect fellow rollers I trust in @openQA to find these issues and block 6.13.1 from hitting @AeonDesktop so I’ll just keep on rolling :)
it's 2025. blows my mind there are devs out there rawdogging code manually without *any* llm support. no cursor, no composer, no chat, no copilot, not even chatgpt
Hi All!
New release of #distrobox is on the way!
1.8.1 brings lots of improvements and refinements all over the place, in pkg manager handling, nvidia integration and in performance department! 💪
Also many many new contributors! 🎉
Check it out! https://t.co/GInx1rJfBz
@mattfarina Sure.. but I’m not trying to take over the world with Aeon
As long as it’s good enough for me, I’m happy enough
The fact that good enough for me is also better for SUSE IT is also a nice bonus too ;)
@mattfarina Or at least not easy while still being secure
And given I use Aeon for work, I gotta keep it secure
And I’m pretty proud of how usable AND secure we’ve made Aeon out of the box
Losing Hibernation is one of very few compromises we needed to accept
@mattfarina As soon that swap is populated your encryption keys will be happily sitting there decrypted in swap for someone to steal and undermine FDE
Not to mention that the swap could be modified offline and then that would also undermine Aeons boot chain validation..
So.. yeah, not easy