I'm not sure there ever was a "popular" migration away from the GPL.
Certain companies (Apple) avoid GPLv3 because of the patent clause, sure. But BSD/MIT/etc. licensed code has always been around and that style of license has always been popular.
There does seem to be an uptick of FSF fanboys recently talking about how horrible non-GPL software is, but that's not new either.
Unless someone vibecodes a new OS and convinces everyone to use it, we're stuck with what we got. Reaching feature parity with Linux and then debugging it to the point where it'd be usable is a gargantuan undertaking.
NAT and CGNAT break the basic idea of how the Internet was designed, forcing everyone into servers and consumers. We've just become used to it, and most people have never experienced it any other way.
The Internet was supposed to be a purely peer-to-peer network, where the addresses on each side of a connection pointed to an end node. That's why protocols like FTP or SIP break when NAT is used, and why you have to play games with port forwarding if you want to run services from your house (assuming you have a public IP address at all).
It's slightly unrealic idea though, as most of internet users are consumers, and that's the role they really prefer. That's why Dropbox gained popularity in spite of, you know, the fact that we all can do it with FTP.
> It's slightly unrealic idea though, as most of internet users are consumers, and that's the role they really prefer.
Because just about all applications are currently architected in such a manner.
When Skype first came out many moons ago it allowed peer-to-peer connections with clients, but a lot of clients were behind NAT (especially ones that could not do PCP or UPnP), so Skype had to come up with the notion of "super nodes" that could do relaying.
Protocols like STUN/TURN/ICE/etc had to be developed to deal with all of this blocking of traffic.
If clients could know their 'real' addresses and allow things like PCP (which is often needed for (e.g.) video games), then perhaps there could me less strictly consuming and more collaborating.
We couldn't do it with FTP. That's kinda the point. We didn't have static IP addresses for every machine or the entries in DNS to go with them.
The whole idea of "consumer" and "server" nodes is so baked into how people think about networking they don't even realize it. But that's not how the Internet was intended to be in the first place.
You absolutely can do it within the existing paradigm, in a number of ways, actually. Search for iroh, or DynDNS for example.
And if you seriously believe that Dropbox appeared because of NAT, and not because people prefer out-of-the-box solutions, I can only suggest you to go out of your bubble, and discuss technical issues with random people.
"Intended" btw is not even an argument. Internet wasn't intended for many things which we happily do here.
I'm well familiar with DynDNS. I used to run it before I got a real domain. It can't tell the difference between my laptop and my workstation, since they're both behind the same IP. I wasn't aware of iroh, but having looked it up, it's just a hack to get around problems that NAT has caused.
And yes, Dropbox does exist because of NAT, or more generally the fact that "consumers" are second-class citizens on the Internet. If everyone had a publicly routed address and an entry in DNS - which is how the Internet was originally envisioned - we'd have solutions that don't require a third party server.
Both of your examples just show how deep the Stockholm syndrome is. IPv4's limitations have shifted the way people think about networking so much that they rarely even realize they're doing it. But this isn't the way it was supposed to be. "Intended" is completely valid when we're talking about how something has strayed from its original design and the ramifications of it.
I'm not naive enough to think that we can ever get rid of the "consumer" and "producer" ideas that have crept into everyone's head. But it's important to remember that these ideas came about only because of limitations in the protocol, not because they're some kind of natural law of how global networks function.
Yes, and DynDNS too. Which is fine, cause it works, and that is what I said. The claim to which it replies is that people have to pay to Dropbox cause poor souls were stopped from sharing files using existing technologies like FTP by the damned IPv4, and not because they simply prefer an out-of-the-box GUI thing.
There were out-of-the-box GUI experiences, like Apple's "Back to my Mac", that never worked right because of all the issues with poking through NAT caused by IPv4.
Relying on peer-to-peer relays also doesn't scale, which is why Skype dropped its supernode architecture.
> That's why Dropbox gained popularity in spite of, you know, the fact that we all can do it with FTP.
Dropbox gained popularity *BECAUSE IT MADE IT EASY TO DO THIS WHEN YOU'RE STUCK BEHIND NAT TRASH*. By the time it was even a thought in anyone's brain the internet had already been ruined by that garbage.
It would never have existed in a world without NAT because it wouldn't have been needed, syncing data between computers you owned that all had publicly routable addresses is a much simpler problem.
Every ISP that has CGNAT v4 without providing full v6 needs to be shut down. They are either incompetent or actively choosing to make their users' service less useful to restrict them and/or encourage "upgrades". Internet service has a public routable IP address, period.
>it would never have existed in a world without NAT because it wouldn't have been needed,
I'm sorry, but this claim is one of the brightest examples of false consenses effect I've seen in ages. People generally just prefer an icon on desktop to click/tap. And that's the reason Dropbox found its audience.
Now imagine if you didn't need that icon and Windows Explorer (or whatever file manager you use) could just connect to wherever your file is. Maybe through a "Favorite."
Then imagine the security implications of trusting windows to serve just some selected files over FTP and never have any security hole that exposed other files or allowed RCE
> syncing data between computers you owned that all had publicly routable addresses is a much simpler problem.
In no way am I denying that people would like to solve the same problems easily. What I'm saying is that it would have been a much simpler problem requiring much less infrastructure. An application like SyncThing that works without any central infrastructure would have been an order of magnitude easier to implement in a world where every internet connected device had a unique routable address.
> Only today we would have put everything behind something like NAT anyway because your devices would be getting hacked constantly.
So the security "provided by" common 1:many NAT comes from the fact that 1:many NAT inherently requires stateful connection tracking and by its nature traffic coming in from the "1" side without an associated connection or rule has nowhere to go, effectively denying any other traffic by default from the "1" side which is almost universally the untrusted side.
Do you know what else has stateful connection tracking and deny-by-default rules on untrusted interfaces? Every single firewall that's worth using or even was at one point worth using in a year starting with a "2".
So yes, in a world without NAT we'd still have stateful firewalls blocking unsolicited incoming traffic that had not been specifically allowed. Those who wish to host public services will still need to configure rules to allow that traffic in unsolicited but those rules will be simpler than NAT port forwards because there's no address translation involved. Anything else wanting to generate on demand temporary connections between systems will be able to do so simply by having each system perform a basic hole punch, sending traffic at the other at the same time with the same pair of ports, and expect it to work again in ways much simpler than what's necessary for reliably doing the same in a 1:many NAT environment.
1:many NAT makes nothing better, it only makes things worse. It's a bad thing and needs to go away as quickly as possible.
---
1:1 NAT is an entirely different beast, it can be entirely stateless and thus has no has no negative impact on most protocols that don't try to communicate address info in-band but also that statelessness means it doesn't inherently provide a firewall effect.
> It's slightly unrealic idea though, as most of internet users are consumers, and that's the role they really prefer. That's why Dropbox gained popularity in spite of, you know, the fact that we all can do it with FTP.
Dropbox gained popularity because none of us can or want to bother to do it with FTP, with the exception of a very small and determined minority.
Why do you think that even FANG engineers use cloud storage systems such as Dropbox/iCloud/OneDrive/Google Drive/etc. Can't an elite software engineer put together a FTP server?
Why do you think Dropbox et al are still a thing in spite of projects such as Syncthing?
This is not the only instance where user experience and convenience show their value. Look at Docker, for example. The "aktually" crowd will be fast to say that anyone can do the same with chroot et al, but they will again be missing the whole point. It's the same thing why Microsoft tried to invest in Aspire even though Docker is here.
It's like complaining that people can buy bread when all they need to make their own is flour, water, salt, and yeast. That's completely besides the point, ain't it?
I think you're taking the "FTP" part a bit too literally here. No one's suggesting we'd jump in a terminal and type in FTP commands manually or even use the FTP protocol itself - we've got better options today, and we'd have even better options if the Internet had had global node-to-node connectivity all along.
It'd likely just be built into your operating system's tooling. Your file manager would be able to access other machines it can authenticate to, or you'd automount remote directories on login, etc.
The reason people use cloud storage systems for moving files around is because they have to. A 3rd party server is required because we don't have node-to-node connectivity.
Hell, we'd likely have had cloud storage options sooner because people wanting extra remote storage would totally have been a thing.
To add to what everyone else is saying, most Lisps support redefining functions in a running application. Instead of the code/compile/test loop most languages use, you can create Lisp programs iteratively from inside the program.
It's really quite neat. Emacs is an easy way to play around with it, but if you're a CS language nerd Racket might be a good fit for you. And if you want this type of environment but without all the parentheses and polish notation, check out the Smalltalk implementation Squeak.
They cannot. Linux success has nothing to do with GPL is in direct contradiction with I really think the license has been one of the defining factors in the success of Linux.
Except you left out an important bit of the OP's statement, where he/she is talking about Linux's success over BSD specifically.
When Linus was talking about the GPL being part of Linux's success, he was talking about Linux's success in general. And yeah, the GPL most likely is a big part of Linux's success.
However, if 386BSD had been freely available in '91, Linux would likely never have had the opportunity to build the developer base needed to take it from a student's neat project to a viable operating system.
In context it seems they're concerned about clear ownership of the code. It's lumped in with rules about not submitting code that might not have clear licensing or ownership. Here's the specific part from NetBSD's Commit Guidelines:
Code generated by a large language model or similar technology, such as GitHub/Microsoft's Copilot, OpenAI's ChatGPT, or Facebook/Meta's Code Llama, is presumed to be tainted code, and must not be committed without prior written approval by core.
A lot of us grew up back when "he" was first being replaced by "he/she" (or just "her"). We'll get used to "they" as we encounter it more and more in daily usage. Just give it time.
Maybe, but default masculine was way more common. That was still taught as proper usage in the 80s here in the US. He/she was its most common replacement until fairly recently.
Maybe! I prefer he/she in this context, which is why I wrote it. I also enjoy Matt Levine's habit of using `she` for unknown gender. If that makes us sound anachronistic someday, I accept that.
My guess is that the initial response by MisterTea was an attempt at language policing, and this whole thread is a waste of time.
It's not a waste of time if you enjoy debating about it!
I think he/she will become outdated soon, if it's not already. I don't think anyone really anticipated there'd be a global debate about gender identity. Regardless of how anyone feels about that particular topic, it's not going to go away. Either everyone naturally shifts to the more inclusive "they" or people will continue to clamor for it.
Matt Levine's not alone in his use of "she/her" - it's actually fairly popular in modern technical writing, I've found.
No, I'm afraid you really are stuck in a culture war. As the above poster said, "they" truly has been a gender-neutral singular or plural pronoun for hundreds of years.
For example, someone two blocks down the street is doing something weird. "What are they doing?" is a perfectly grammatically normal reaction to seeing this.
So if someone said "what are they doing?" about someone some distance down the street, you would find that objectionable? I can't really think of a less awkward phrasing. "What is that person doing?" "What is he or she doing?" Those both seem like unnatural ways to phrase the question. What would you say in this scenario?
You may have heard this from Culture War-adjacent content. In reality, this is wrong, and you would struggle to find a real employed academic who agrees with you.
Also, languages aren't dictated by a standards body like C++ is. The rules are written to capture the way the language is actually spoken. If the rules diverge from the language, the rules are actually the thing that is incorrect! This is the difference between "de jure" and "de facto" rules.
Buddy I was literally taught that in my (British) English class, and later seen it used in this context by natives countless times. If anything, using "he/she" is an ugly unpronounceable abomination.
Using 'they' for an unknown gender has nothing to do with people 'identifying' as they, or anything modern.
It's never been 'he', except in sexism such as 'when the doctor comes he will examine you' (with the doctor's identity and hence gender unknown, but assumed male by profession).
Masculine pronouns were very much the default outside of a few cases (like the "what are they doing?" another posted mentioned). You can say it's due to sexism which is a reasonable argument, but that doesn't change the fact that defaulting to masculine pronouns was the recommended (and most widely used in practice) style.
Seriously, read anything more than about fifty years old. The 1918 Strunk & White¹ stated, "Use the masculine pronoun unless the antecedent is or must be feminine." They argued against inclusive pronouns in the 70s when E. B. White (yeah, the mouse guy) was in charge of the style book, and didn't start recommending inclusive language until the 2000 edition.
The Chicago Manual of Style originally didn't mention it because it was so ingrained in the English language. It only started discouraging its use in 1982, and didn't condemn it until 2010.
Edit: I guess I should state right here that I'm not advocating for default male pronouns in writing. I think "they" is the best replacement. But I was taught "he" and adapted to "he/she" over the years. "They" really only seems to have become prevalent over the last decade or so.
¹That's Strunk and White the style book, not Strunk/White slash fiction.
Maybe! Although I doubt it. Honestly, if you're really curious about it it's best to ask a local language expert if you have access to a university. I'm just an old computer geek with a higher-than-average interest in the written word.
This might make a good subject for a RobWords video, actually.
Your school must have been more progressive than mine, then. The argument was still ongoing in the 70s and 80s, so if you went through school during that era it could have gone either way.
Nuns were the original empowered women, you know. That was one thing the church offered for hundreds of years: if you don't want to be what society tells you have to be, you could always join the church and be a priest/monk/nun instead.
But yeah, I get what you're saying. I don't have any explanation for you, other than he/she was what I was taught in the 80s in Oklahoma public schools.
Certain companies (Apple) avoid GPLv3 because of the patent clause, sure. But BSD/MIT/etc. licensed code has always been around and that style of license has always been popular.
There does seem to be an uptick of FSF fanboys recently talking about how horrible non-GPL software is, but that's not new either.
reply