fish-shell VS HomeBrew

My OS is Linux Ubuntu. My shell is fish and I love it (check out my dotfiles). It allows the creation of functions (a.k.a. aliases) very easily.

from: https://github.com/fish-shell/fish-shell/issues/7152#issueco...

Not sure if you’re being sarcastic or not, but the actual project page is very useful: https://fishshell.com/

The OP is the equivalent of a changelog, which isn’t going to be terribly helpful to the uninitiated.

Shell tools, including, zsh, fish, etc

For part one, I noticed the input being almost valid Elm code, so I wrote a few lines of Fish to generate an Elm program. Then ran it with elm repl. Elm allows out of order variable declarations so it did all the work for me.

The fish shell (https://fishshell.com/) and its fantastic auto-completion. It now replaces bash as the default shell on all my machine and is the first program I install when connecting to a fresh cloud instance.

Turned the input into JavaScript (using Fish) by replacing noop with cycle() and addx with cycle(); cycle(); x+=, and then executing it.

In case you're not not aware of it, virtually all devs on mac use homebrew. I slide nearly seamlessly between WSL and mac depending on whether I feel like using my desktop or laptop at the moment. The differences largely boil down to whether I apt install or brew install things. And as much as I'm loathe to admit it, vscode + vim plugin these days gives emacs + evil a pretty good run for the money when it comes to extensible IDEs.

There’s no practical difference between trusting that a popular GitHub account hasn’t been compromised (see: https://brew.sh) and your distro or other package managers haven’t been compromised when it comes to machine setup. If security is that much of a priority you run your own mirrors and don’t pull from public repositories/registries. IME you want to do that for availability anyways if this is for work. Nothing worse than a failed build for a hot-fix because some package registry is temporarily offline.

Others have offered solutions, but for future reference the actual Terminal commands that failed would be useful; "File not found" sounds like a path error, "Command not found" sounds fixable via Homebrew or Macports

TL;DR, about the section that states software from other UNIX-like OSes is hard to port to MacOS, how about homebrew and macports?

First, you’ll want to install some base dependencies for your operating system. We will use brew 27 for this. If you don’t have brew installed you can do so by running:

Prerequisites: Ensure you have Homebrew installed on your computer. It is a package that enables you to install various applications not provided by Apple.

Get it with Homebrew:

I installed iTerm2 and zsh shell with Prezto and I love my command line on OSX I use homebrew to install any tools that are missing and use pyenv to manage my python version (which I also do on Linux) that and the clang/gcc from the OSX command line tools and I pretty much have a full Un*x shell for anything I need to do

Personally, I like using Terminal to get things done lol. Before you continue reading, please note that I only know how to do this with homebrew and terminal...

homebrew is the most popular package manager on MacOS. It's painfully slow compared to linux package managers but it works. Macports is an alternative and Nix works on MacOS as well. They can be used to download both terminal and GUI applications.