I use Fish. So not an exciting news for me.
I use Fish too :) And I haven't really connected with zsh. I've tried. However I think this is good news for Fish too. It's the beginning of a long-overdue un-Bashifying.
Use zsh as the default shell on your Mac
151–160 of 252 posts
Re: Use zsh as the default shell on your Mac
#152Earlier quoted context omitted.
Can we get a modern python version while we're at it?
They're just going to remove it completely: > Scripting language runtimes such as Python, Ruby, and Perl are included in macOS for compatibility with legacy software. In future versions of macOS, scripting language runtimes won’t be available by default, and may require you to install an additional package. https://developer.apple.com/documentation/xcode_release_note...
> Use of Python 2.7 isn’t recommended. This version is included in macOS for compatibility with legacy software. Future versions of macOS won’t include Python 2.7. Instead, it’s recommended that you run python3 in Terminal. (51097165)
and
> LLDB’s Python scripting is now based on Python 3. If you are using Python extensions that aren’t compatible with Python 3, they will break. To help with the transition, you can run in Python 2 mode by setting a default
So looks like python 3 will become available and default
Re: Use zsh as the default shell on your Mac
#153Earlier quoted context omitted.
Shout out to the fish shell which can do all the fancy syntax highlighting and show command options out the box with no plugins
I used fish for a while. It was nice but way too many compatibility issues. Zsh is a nice compromise.
IMO compatibility issues are the result of conflating a CLI with a scripting language. If a script was written for bash, run it with bash, not fish or zsh. I can withstand having two shells installed.
Re: Use zsh as the default shell on your Mac
#154Earlier quoted context omitted.
Everyone has heard of Visual Studio, and nobody that has to use it wants to. Just because you have Stockholm syndrome doesn't mean everyone else has to have it too ;-)
I'm really suprised at this comment. I'm confident most of the .NET community is very happy with Visual Studio. In my opinion, Visual Studio massively outclasses Eclipse, VSCode and Netbeans. It even makes IntelliJ (which is pretty great too) look a bit inadequate. (I use Emacs these days though.)
>from a development standpoint
>I'm confident most of the .NET community is very happy with Visual Studio
.NET is not the only ecosystem people develop for. There are embedded C/Forth, web frontend/backend, written in Java, Scala, Ruby, Python, other stuff. VS sucks for nearly everything safe C#/C++ for windows.
Besides, even for C# people use an additional plugin, resharper, so VS is not enough even for its target ecosystem.
Re: Use zsh as the default shell on your Mac
#155Any beta testers here able to confirm whether Terminal.app supports True Color now?
It doesn't look like it.
Re: Use zsh as the default shell on your Mac
#156For those wondering why Apple is allergic to GPLv3 code: there is a clause in the license requiring you provide a way to run modified version of the software which would require Apple to let users self sign executables.
This reason doesn't make sense, though: I can modify, replace, and overwrite the bash that comes with the system, and self sign it with a certificate of my choosing.
Re: Use zsh as the default shell on your Mac
#157Earlier quoted context omitted.
That's my point. Why can't Apple ship an updated userland built in, through the Store, or as a download triggered by a command line (like XCode is).
Because GPL v3 says you have to run modified binaries and that means Apple has to give its private keys.
No? You just resign the binary with your key.
Re: Use zsh as the default shell on your Mac
#158Earlier quoted context omitted.
Not at all. You've always been able to run your own software. At worst, it's toggling one option off in preferences that stays off forever thereafter.
Not anymore. Since 10.12 Sierra the GUI option to turn off Gatekeeper is gone, you have to use command line to turn it off. And now App Notarization is making it harder still to run your own software.
GateKeeper only applies to software you download from the internet, and only then in a couple of very specific cases.
Re: Use zsh as the default shell on your Mac
#159Earlier quoted context omitted.
Sorry, how is that a problem? Users can build and execute code on their own Mac with XCode.
Perhaps Apple's vision for the future is one where you can't do that (ex: App Notarization seems to have us heading in that direction.)
You can run your own code on iPad these days: I don't see this change happening anytime soon.
Re: Use zsh as the default shell on your Mac
#160Earlier quoted context omitted.
I used fish for a while. It was nice but way too many compatibility issues. Zsh is a nice compromise.
IMO compatibility issues are the result of conflating a CLI with a scripting language. If a script was written for bash, run it with bash, not fish or zsh. I can withstand having two shells installed.
You can, but if Fish's value proposition is ease-of-use, then people who can't withstand that need to be able to use fish easily still. Not being able to run `PORT=5000 yarn start` or `make && ./a.out` or whatever snippet you copy-paste from the web without understanding are going to be a big pain point for newcomers to fish.
Don't get me wrong, I'm a happy fish user myself. But breaking backwards compatibility with shells from the past 40 years and then saying "you're doing it wrong" is not how to make easy-to-use software.