Change my mind.
Companies are just taking BSD code and don’t contribute to it. At the end they’re selecting Linux even if there’s licensing risk and they have contribute to code. Why? Because Linux have a lot of contributors, that makes it much more advanced system with more features. Also companies which want to support Linux don’t have to worry that someone would close their code or code they funded with money. It’s not about competition but collaboration. GPL license allowed us also to sell own open-source solutions.
FreeBSD, OpenBSD and NetBSD are behind Linux. I love that systems (especially OpenBSD), but I don’t see a point in contributing or donating to them. Instead of being ready to use solutions they’re trying to be base for commercial closed-source products and it would be great as contributors could get something from that, but they get nothing.
I understand that BSD see closed source as something cool and way to commercialize software, but in today times where a lot of devices have 24/7 access to internet, microphones, cameras and at the same time to sensitive data it’s extremely dangerous. Closed source is used to hide backdoors, acts of surveillance and keeping monopoly on market which obviously stop evolution of software.
Please tell me how BSD license can be good solution for operating system. It’s not about offending BSD, but as someone who love open source software I hate closed source software I would like to know how I can defend this license.
It’s really just a difference of opinion. GPL enjoyers such as myself believe that Free software is the best and it should be kept free with a copyleft license. BSD license enjoyers also love Free software, but they believe in putting next to zero conditions on their software. They’re just happy if their freely released software is used to make anything better, even if it means proprietary projects incorporating it and not contributing.
Companies are just taking BSD code and don’t contribute to it.
There isn’t a lot of evidence of this.
At the end they’re selecting Linux even if there’s licensing risk and they have contribute to code.
This is at odds with the first statement. Companies also aren’t contributing as much code as they should.
Also companies which want to support Linux don’t have to worry that someone would close their code or code they funded with money. It’s not about competition but collaboration.
Yeah, inertia is a thing. It’s why Windows is so dominant. The BSDs were rather competitive with Linux back in the early ‘90s - ‘00s.
This might have been a reason in the ‘90s IBM picked Linux as the Unix successor, but now it’s about inertia and a baseless OS is pretty handy.
It was also never about collaboration. It was always MAD doctrine. Each company had a pack of lawyers ready. The GPL isn’t the most battle tested.
GPL license allowed us also to sell own open-source solutions.
This isn’t the flex you think it is.
Instead of being ready to use solutions…
The BSDs are full operating systems. Batteries are included in the repo.
Linux requires adding lots of other software to make the kernel useful. When people say “It’s GNU/Linux”, this is what they mean. The Linux kernel + the GNU tools make an OS.
…they’re trying to be base for commercial closed-source products and it would be great as contributors could get something from that, but they get nothing.
They are not. They are existing as their own projects. ☺️
Most FOSS devs get nothing. 🤣 GPL, BSD, Apache… It doesn’t matter. The capitalists plunder the commons making money off of other’s hard work.
I understand that BSD see closed source as something cool and way to commercialize software,…
They really don’t. They just want to work on their projects in peace.
…but in today times where a lot of devices have 24/7 access to internet, microphones, cameras and at the same time to sensitive data it’s extremely dangerous. Closed source is used to hide backdoors, acts of surveillance and keeping monopoly on market which obviously stop evolution of software.
Ummm…. That’s not BSD specific. FOSS software gets used for this as well. All those surveillance devices are probably running some sort of Linux.
There are binary firmware blobs and all sorts of stuff. The Linux kernel is GPLv2 specifically to allow this.
The DMCA’s anti-encryption circumvention is used to chill software evolution and lock up code more than anything. BSDs only ask that people don’t GPL their stuff.
Companies play all sorts of games with code, and there isn’t a guarantee that what is in the repo is what people are running. We need reproducible builds to know the software is clean, and without that, software is not trustworthy.
This is bigger than the license on the code. This is about processes and culture.
Please tell me how BSD license can be good solution for operating system.
The code is still open, and the repos will still exist if a fork is created. Sony forks FreeBSD for PS6, and nothing happens to FreeBSD. It still exists, and it still works. The added bonus is not having to deal with Sony, or other people, trying to upstream stuff that doesn’t make sense outside of the PS environment and would have questionable value to others.
There are lots of ways companies get around the GPL, and most are GPL sanctioned.
Starting a company, use the GPL. Starting a project for fun, use whatever because the companies are going to steal it anyway if it’s good.
FreeBSD, OpenBSD and NetBSD are behind Linux.
Look, I dislike permissive licenses too, but you need a source to back this claim up.
Right now, each BSD does something special, that Linux (distro’s) can’t trivially replace, even if the usecase is more niche. NetBSD Dev’s make efforts to get it running on many devices as they can. OpenBSD (and it’s subprojects) are highly secure, moreso than Linux. Who do you think makes our beloved OpenSSH? OpenSSH noted for having very few vulnerabilities over it’s two decade long existence, and OpenBSD itself is similar, which is insane because there are products with multiple bad vulnerabilities every year (Linux being one of them…). This is due to a highly security minded architecture - one that Linux lacks.
FreeBSD is like Linux before systemd. I like systemd, but systemd is really trying to be kubernetes on a single node. I like systemd because I like kubernetes, but I understand why someone wouldn’t like it, and I question if “single node k8s” is the best architecture for a single server or personal desktop. The ports system results in freebsd packaging many server services that aren’t packaged on Linux. Being able to manage those through the system package manager, and the conviniences that provides, is nice.
Different, and not popular don’t mean bad.
Android has BSD-like permissive license. It’s open-source, but is also very very commercial. Google needed it to be open-source so phone manufacturers would adopt it, they all got burned on Windows Phone and Symbian and did not want another closed source OS that they could not modify for their specific hardware.
Should probably be asked in an active BSD community if you want a real and well informed answer.
There isn’t much sense in it at all.
This debate is about as old as the existence of free licenses. I doubt anyone will have anything new to say in this thread.
One aspect that isn’t raised very much is that for a company to maintain software (including their own fork of any software however licensed) costs developer time (= money). It may be cheaper to contribute back anyway, no matter the license, just in order to outsource that effort. If we are talking about software where this is true, companies have an incentive to work with the existing maintainers even if they aren’t legally obliged to.
This is the thing that people overlook. Carrying a patch set is a burden, and companies have to maintain the patch set. Upstream isn’t going to care about the patch set because not their problem, and they will make changes which benefit the open code in their repos.
I’ve seen a company modify a FOSS project to fit their needs and get stuck with a multi-year old version because their changes were incompatible with never versions. They had to scrap the system and start over.
Regardless of license, not contributing upstream creates a problem unless the company has the stomach to support the whole thing on their own.
I understand that BSD see closed source as something cool
‘You understand’? Where did you get that idea?
The argument is not, and was never, that closed source is cool. The argument is that strong copyleft, while based on a noble goal, ends up hindering development: Here’s OpenBSD’s take on it. (CTRL+F for GPL).
So if they see closed source source as something not cool why they allow to close their source code?
Of course, strong copyleft licenses sometimes can hindering development for example GPL and CDDL license conflict don’t allow adding ZFS support to Linux Kernel. But it will not help with development when corpos are more taking than giving to project. Just look where’s Linux and where’s BSD - you can see how GPL hinder that development.
And why they see GPL license unacceptable in commercial use? For me unacceptable is to close source code, no matter if it’s for commercial use or not. For me open source is alternative for that shitty closed source commercial software. If I’ll try to make my own open-source commercial product based on BSD license it would be impossible. Competitor with more money for marketing will just take and close my source code, add few improvements then sell it as own product. Why I would like to risk that?
If that’s not the argument, then the alternative is that they’re hopelessly naive.
I agree, and in that same vein, Linux really should be AGPL as well.
This is the permissive vs copyleft debate. And it’s old as time. I suppose there’s a lot of nuance with licensing. If you’re a company at the receiving end, you probably love permissive licenses. They’re easy, offer the maximum amount of flexibility and freedom. It’s so short you probably don’t even need a team of lawyers… If you write software, it’s a bit more complicated. Do you want to cater to those people, make it as easy as possible to adopt your software? Then maybe consider BSD/Apache/MIT. Do you want to build a community, stop your competitors from just taking code? Want to try to ensure it stays open? Then maybe consider a copyleft license.
I sometimes don’t care. Write some stuff for me (as a hobby) but that’s my entire motivation. I don’t care what people do with the results of my weekend of effort. Never plan to hire a lawyer or bother with it in case something happrns with it. Or it’s just a pile of snippets. I’ll dump it for other people to use and release that either WTFPL or some other permissive license. People can do whatever they like with it. With the stuff I’m a bit more proud of, or I plan to return to, I’ll choose AGPL.
I suppose with operating systems, it’s a bit similar? I mean there is a community for both ideas. Seems there are people who like either of them. They’ll have slightly different ideology, tasks to accomplish and different goals.
deleted by creator

deleted by creator
Oh I don’t either, just a perfectly fitting meme. Especially when you look at it from the angle of “replacing things that already work” and “rewriting everything in it.”
deleted by creator
I mean as far as myself. I never got it. Im not really a developer but if im not being paid diretly for my work or building a business around it and keep the ip for myself. If im putting it out there I want to do share and share alike. Using bsd is great and im glad it exists but I would never put anything under the license myself if I was making the call.


