I previously thought zsh fit the Apple ethos and aesthetic the best with its nice completions and clean(er) syntax.
Now I wish they’d start shipping fish as it provides such a nice experience out of the box, and is gplv2
I would not care either way since I just use ohmyzsh, their github page has a shell oneliner to install it, good enough for me
Edit: to clarify, any shell script that is executed will define its own shell to execute with (the #! line).
There may be some issues if scripts have declared their shell as /bin/sh but they use bashisms, and then /bin/sh isn't provided by bash anymore, but honestly that's not necessarily related.
The discussion here is about changing the default login shell for interactive user accounts to fish.
If they did this though, it would be nice if they would use dash for /bin/sh, but I'm not sure how that's licenced - possibly gpl3 too?
Ironically, the primary developer of fish is an Apple employee. This is probably a significant reason why it's GPLv2 and not v3!
Also, I had no idea the fish dev worked at Apple. I have no hopes of them going with that as a default, but I could certainly see them shipping it as part of the os...
Source code: https://github.com/fish-shell/fish-shell
I remember the days where each login into an UNIX system would give me a totally different shell.
But all relevant ones were installed, so it was only a matter of having the right shebang paths.
So if Apple has a deal with a patent troll which has a an obvious broken patent that covers all and every program (but which would fall apart if challenged), then apple could in theory get into trouble with the troll if they distributed GPLv3 software.
There is precedent for the latter. When Red Hat paid off the Firestar troll, it negotiated a patent license for all recipients of the software, including upstream and derivative versions.
Discouraging individual patent deals with a troll while leaving the rest of the community (from whose software you benefit) vulnerable doesn't seem like a bad thing to me.
That sounds like an odd thing to wish for in software where you are the user. That's asking for less freedom.
So why would you do that?
> Shipping old stuff is unacceptable and it's not like we can't install it if we want it.
I can't see how 1. this is related and 2. how Apple would bother putting in the effort to replacing its full toolchain with completely different implementations when they can't even bother updating the one they already have.
Basically... This is all on Apple's hand.
But if you want a modern, updated toolset which you know will be kept up to date, I know there are lots of Linux distros out there which can deliver what Apple seemingly can not.
First, the BSD license offers more total freedom than the GPL does. I say this despite liking both the FSF and the GPL.
Second, I would rather have up to date version of good BSD software than an old versions of good GPL software.
That's objectively false. GPL provides more end-user freedom. BSD provides more developer freedom.
There's not a single license which objectively and universally offers more freedom.
> I would rather have up to date version of good BSD software than an old versions of good GPL software.
False dichtohomy. That's comparing rotten apples to ripe oranges.
You either have to compare old GPL to old BSD or new GPL to new BSD.
And as an end-user I would prefer both new and GPL.
I disagree. Forcing people to do things is not "more freedom", although the GPL's goals are laudable.
"False dichtohomy. That's comparing rotten apples to ripe oranges. You either have to compare old GPL to old BSD or new GPL to new BSD. And as an end-user I would prefer both new and GPL."
Unfortunately, new and GPL is not an option. But this result is what the FSF wanted when they created the GPL3.
This debate has been had a million times.
Every time reasonable people agree you have to choose one or the other.
You can't have both.
I see no reason to re-iterate that debate though. I'd just like to point out that your view is not the prevalent nor accepted one.