@klme@fosstodon.org@itsfoss@mastodon.social Actively discourages the use of the GPLv3 (the best free software license we have today), and takes all the credit for creating "an operating system" (GNU created an operating system, he only a kernel).
Also Linux is not even a free software project. It contains many proprietary blobs because Torvald's has no ethics.
@SuperDicq@itsfoss@klme that wouldn't have happened at all, imo. there could be some hw support for server stuff but not more, less than what we have now
Why are people in our current timeline still using the Linux kernel despite it being copyleft licensed (but under the GPLv2) when they could avoid copyleft completely by using something like NetBSD instead?
Because NetBSD fucking sucks and everyone knows GNU/Linux is technically superior.
@mischievoustomato@klme@itsfoss@SuperDicq if we think of GPLv2 being less restrictive to companies (which invest into Linux development the most) and therefore making it more appealing...
we have also have other free operating systems that were not helped by permissive licensing, even though it's less restrictive than GPLv2 and again must be even more appealing
I don't think companies would flock to NetBSD. They'd do what you see with FreeBSD: rip out the parts they like (typically the TCP layer) and repackage it into something unrecognizable (Wii's OS, PS4, etc.) That's specifically the embedded space. Linux did well in the desktop and server space because of driver support more than anything, and it came up before the VM farm (a.k.a "cloud") era.
It's been a long time since I looked up the Tivoization/GPLv3 debate. What would have that license done in modern terms? Would we not have linux-firmware? Would Android still be just as annoying to make custom ROMs for? You could make the argument then we'd see fewer binary blobs and less need for things like coreboot ... or companies would have found more interesting legal ways around those limitations.
As far as Linux foot-gunning themselves more these days, there's the whole zfs/write_cache_pages thing with the kernel 6.18:
>Why are people in our current timeline still using the Linux kernel despite it being copyleft licensed (but under the GPLv2) when they could avoid copyleft completely by using something like NetBSD instead?
Because it was the better solution that still allowed companies to run it on whatever they wanted without any meaningful restrictions. And GPLv3 restricts that with Tivoization. It's as simple as that. You restrict companies from using it, companies flock to something else. The OS you are currently using was made possible by companies using it and contributing back, something which would very likely go away with GPLv3.
And the line of thinking that more free hardware would be created is also delusional since most free software advocates lack knowledge to actually create any hardware. And companies have completely no incentive to create such hardware, especially if they can't run a kernel however they want using their own hardware.
>Because NetBSD fucking sucks and everyone knows GNU/Linux is technically superior.
It's also much more complicated and the reason why it won in embedded is because it gained a toolchain in mid 2000's that supported cross-compiling in a reasonably sensible way. NetBSD is still more easily portable, but lacks filesystems useful in embedded like squashfs, jfs and ffs.
Also >NetBSD fucking sucks Portability is bad in your eyes? Just like OpenBSD creating and maintaining core parts of any Linux system (sudo, openssh, tmux), NetBSD did the same.
Do you need UNIX-esque tools to run on some obscure UNIX-like OS, you turn to NetBSD userspace. Do you need to build a package for your OS temporarily and packaging it is too complicated, pkgsrc has you covered.
@klme@fosstodon.org@itsfoss@mastodon.social People who support "open source" are usually not opposed to add in proprietary software into their codebases "pragmatic reasons", like kernel blobs or other binaries.
That's literally the opposite of software freedom.
@a1ba@klme@itsfoss@SuperDicq the thing you conveniently forget is the momentum/intertia linux had due to winning that lawsuit, and the gplv2 being "good enough" in regards to contributing code and using blobs for companies that they just kept working with it.
@phnt@klme@itsfoss@SuperDicq exactly. If Linus went through with licensing the kernel with GPLv3, I probably would've never used Linux in the first place.
Some random Linux dev got assmad about a company doing that to bypass the kernel stupidity while rewriting the driver to GPL and added a quirk to blacklist them. Linux should have been LGPL from the start.
@djsumdog@phnt@klme@itsfoss@SuperDicq > As far as Linux foot-gunning themselves more these days, there's the whole zfs/write_cache_pages thing with the kernel 6.18:
I wonder how hard it'd be for someone to make a kernel patch that turns off all the symbol exporting issues.
@SuperDicq@minidisc.tokyo@mischievoustomato@tsundere.love@phnt@fluffytail.org@djsumdog@djsumdog.com@klme@fosstodon.org@itsfoss@mastodon.social It's kinda of difficult to know what had happened but i see two sides like: - On one point you have that yes more permissive licenses mean the companies can do whatever they want so they will use it more - More copyleft licenses maintain everyone's freedom and make it so everyone can get benefits but companies use it less If the bsd license was good, freebsd or netbsd or whatever would have thrived regardless, but it didn't, as the model doesn't ask anything in return, you basically work for others for free, this doesn't happen in the more copyleft licenses.
@waifu@SuperDicq@itsfoss@djsumdog@mischievoustomato@klme You can still do that same shenanigans you normally do with BSD with Linux. If your Linux patches are only internal and aren't shipped anywhere outside of the company, you don't have to disclose any of them. And if you ship something with those patches, you can play the come to my office for the source code game. The GPL doesn't actually solve anything when it comes to companies not contributing back.
Intel and Netflix both contribute regularly to FreeBSD and if you want a stable storage system or a firewall that won't die randomly, you use FreeBSD. Because ZFS on Linux is a russian roulette and conntrack is garbage.
We'd have a far weaker RHEL, thus maybe we would have a minimal systemd-like thing that is far more modular and no Gnome madness, since RHEL would have been way too financially weak to push its policies onto the wider community, it would need to keep itself on the good side of the userbase, being less able to pay for development, and being less pressured by company contracts
We probably would have some generalized kernel-only GPLv3-compliant drivers that would work with most things in a basic state, but you'd probably need to inject kernel modules or use some userspace driver things to install firmware and unlock all features. Basically Nvidia before it released the open source driver, but on a larger scale and in a more supported way, except on some pure distros
Android would still happen mostly the same
We'd have less corporate Linux and more desktop Linux
@pantherastare@vokainen099@djsumdog@phnt@waifu@itsfoss@SuperDicq honestly ebussy is a god. I don't want people to give their opinions and tarnish the view that gnome has.. I'm incredibly more productive on gnome than i was when i used windows or something similar to that paradigm. Plus it also uses very little resources, especially power.
@mischievoustomato@vokainen099@djsumdog@phnt@waifu@itsfoss@SuperDicq 50% of all gnome hate comes from people groomed into buying a cum stained thinkpad and/or not using the cpu they paid for the rest is people who only really need gui to run video games or had the misfortune of reading one or more sentences written by ebussy
I prefer to use KDE, or XFCE on my machines that are too slow for KDE.
I do not like GNOME simply because it feels like the developers are trying to force a very specific vision of what they think the desktop should look like while not listening to the needs of their users.
It's not a software freedom issue. I do not think it is unethical to use GNOME. I just don't like this model of development. It kinda reminds me of the same issues I have with Mastodon to be honest.
@a1ba@klme@itsfoss@SuperDicq@mischievoustomato >if we think of GPLv2 being less restrictive to companies If you actually read the GPLv2 and GPLv3, you'll realize that neither license contains any restrictions and GPLv3 being a better license, better suits companies.
The GPLv2 in fact totally forbids tivotization; "The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and ****installation of the executable****." (note there are some "creative interpretations" that providing incomplete compilation scripts that compile object code that does not execute (i.e. not an executable) is compiling with the GPLv2 - but really those Linux developers only ever enforce their license against freedom).
Meanwhile, the GPLv3 permits tivotization for commercial-only hardware (as companies wanted that); A “User Product” is either (1) a “consumer product”, which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. “Installation Information” for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
(Quite clearly merely a longer-winded way of stating what the GPLv2 requires, except looser, as commercial-only hardware is excepted).
>even though it's less restrictive than GPLv2 With weak licenses, you do not have any defenses against patent or trademark threats, thus the chances of restrictions with weak software is much higher.
@phnt@klme@itsfoss@SuperDicq@mischievoustomato >You restrict companies from using it, companies flock to something else. Companies are not restricted from using GPLv3 software - they are welcome to use it.
Just like the GPLv2 does, the GPLv3 simply doesn't give companies permission to attack the human race.
>GPLv3 restricts that with Tivoization. Unlike the GPLv2, with the GPLv3, companies can implement whatever tivoization they want with commerical-only hardware.
The GPLv3 doesn't restrict anything - it even grants more permissions than what the GPLv2 does.
>The OS you are currently using was made possible by companies using it and contributing back, something which would very likely go away with GPLv3. Companies really haven't had any problems contributing to GPLv3-or-later packages at the same rate as GPLv2-only packages - although that rarely happens as most companies are too dumb to help themselves.
The server part of the AGPLv3+ only applies if the software is being run as a network service for some users and it's compatible with the GPLv3+ - meaning if it's compatible with GPLv3+, it's compatible with AGPLv3+.
@SuperDicq@itsfoss@RedTechEngineer@klme >If you're running Nginx or Apache on your server it would be really annoying to comply with the AGPLv3. If you don't modify the software - the AGPLv3 doesn't require you to do anything.
A web server is quite good at serving files and it can serve the source code of the modified version just fine (AGPLv3+ software tends to be designed to automate providing the source code).
>this software is running not on my computer, and it isn't SaaSS. The AGPLv3+ doesn't require anything if the computer is not doing a computation over a network service for users (i.e. not SaaSS).
@SuperDicq@itsfoss@RedTechEngineer@klme >If you want to modify the code as a server admin you would have to do additional work It's much easier to include a copy of source code than to make modifications of source code and if someone is going to make a change, they can copy a file too.
>with no benefit to the users of server (they don't need it) The users do in fact deserve the source code - they deserve to know what change the admin has made if they want.
@Suiseiseki@freesoftwareextremist.com@itsfoss@mastodon.social@RedTechEngineer@fedi.lowpassfilter.link@klme@fosstodon.org My SaaSS argument is not about AGPLv3 requirements. It's about the requirement for freedom for the user. If you don't modify the software - the AGPLv3 doesn't require you to do anything.Yes, but that's my point. If you want to modify the code as a server admin you would have to do additional work, with no benefit to the users of server (they don't need it). It's not convenient.
If the software did not do the users computation, then the software is actually private and it's fine if the user doesn't have a copy of the software (and the AGPLv3+ doesn't require providing the source code in that case either).