89
Rust Coreutils cp Ended Up Breaking Ubuntu Image Builds With Latest Incompatibility
(www.phoronix.com)
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
No, it doesn't result in less open source. It results in more proprietary. You have the same amount of open source as before and didn't LOSE anything. The MIT License allows for stuff that wouldn't be possible otherwise and it is easier to understand and teach too. I argue that using MIT does not automatically or mostly result in worse outcomes than if they used GPL. Mostly it works fine.
That does not mean MIT is perfect. Like every license, it has its own strengths and weakness and should be considered like any other license. Also you can still go from MIT to GPL, in case you change your mind later and want to enforce GPL on any project based on it, but not other way round.
Not nessesarily think about comparing macos with aosp.
Since android used linux which is licensed under the GLP they had to make it open source and they contributed back to the open source community.
Macos on the other hand used a lot of software from freebsd and other bsd projects. Since freebsd isn't free software macos never contributed back to the community since they didn't have to.
Not using the GPL can result in less open source.