Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
Don't break userspace. 32-bit support should never be removed.
Easy thing to say when you're not the one donating your time for free.
I love what Valve is doing for Linux, but longer term, the onus is on them to solve the 32-bit compatibility layer issue (a-la Proton for win-to-linux, as well as their upcoming x86-to-ARM layer).
Expecting all distros (who again, are staffed mostly by volunteers) to do this work separately (i.e. duplicating all that work), for all time, is a big ask.
By that logic we should never remove anything legacy ever. It don't work like that.
Userspace is allowed to break themselves
That's a kernel saying. A bit unfitting to repeat it for the distro that builds said userspace.
Isn’t the context of that quote around the kernel and kernel space vs user space? I don’t see how that thought really extends to distros that simply implement the kernel as one of their packages.