view the rest of the comments
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.
I mean RHEL has been kinda doing it with GPL for a few years. They share the code with you if you have a subscription, since they have to, but if you share it with anyone, they'll void your subscription contract. With MIT you can skip that scheme altogether and just make version closed source.
Like... Why else would they use MIT here? They could have just used GPL for the Rust coreutils.
Because GPL is not compatible with everything.
GPL for separate tools is compatible with everything. It only becomes an issue if you're shipping a custom version of a GPL tool.