I’ve been using Fedora for ~7yrs now as my main work driver. I’m in a mixed *nix/Windows environment for work so it does the trick. I will use a combo of Fedora and Windows w/WSL enabled at work. It’s gone well for me so far. Fedora “just works” and hasn’t presented me with issues I’ve ran into with distros like Debian or Arch.
At home I mostly use QubesOS though. I’m in love with the compartmentalization and privacy options at hand when I’m running VMs on there. If I want to test something out I can always run it in a disposable VM. Creating new VMs for things like multimedia or communications is a wonderful option. A recent example of a great use-case was for a Zoom install as I was being forced to use it for remote chat at times. With Qubes I was able to contain the Zoom in an AppVM completely dependent from any other applications and files on the system.
tl;dr - Fedora in the streets, QubesOS in the sheets.
Working from home, continuing to learn SaltStack, and working on my pi-hole blocklist: https://twitter.com/RooneyMcNibNug/status/1246197954207154176
Are you using Void with musl or glibc? I heard that Emacs support under musl isn’t that great, so if you’re using that, could you comment on it?
Hey rocx, I second your list. But what advantage do you see on
zsh? from my perspective, zsh has better features also who can forget
But what advantage do you see on fish over zsh?
Made the decision with a dartboard. Mainly using a stock Fish setup. The ability to
C-e to finish an autocompletion from history is nifty.
Allow me to chime in. I have used bash, zsh+omz, and fish shells, so would love to share my experience. My most current shell (for over 2years now) is Fish, and I absolutely love it.
fish is lightweight. It is snappy. zsh tends to slow down when you have a lot of plugins enabled.
you may need to install the autocomplete plugin in zsh, but it is baked right into fish. The tab-completion in fish doesn’t just parse through your history and available packages to suggest commands. It also allows you to autocomplete switches for commands, along with a summary of what switch does what (uses the man pages of the command).
ls -brings up
h, A, l, f, O, xas a list with the summaries. Useful when you need hints while executing pip/npm/docker commands or anything else.]
ls /va/li/gi, auto-expands the arg to
ls /var/lib/git. Useful when you know where to find what, but dont want to type in a lot]
configuring zsh to your taste takes time (if you dont have the dotfiles), and those dotfiles tend to get large pretty fast when you start copy pasting stuff into them. On the other hand, getting up and running with fish is a breeze. It also has a ‘browser mode’, where you can configure the prompt, theme, aliases and other features using a friendly web-interface.
syntax highlighting is native to fish, and is very fast. I have seen zsh slow down or take time to process what’s written, but fish highlights it almost instantly.
a lot of things in fish are configured using functions, which you can define and save separately. no need to have everything in one long file.
you can set and unset env variables temporarily or permanently, depending on your use-case.
zsh extends bash. fish is entirely different.
the scripting language in fish may not be entirely POSIX compliant (one tradeoff you have to make for speed), but the scripts are neater and cleaner. (think python vs C++). Neater organized code.
fish is definitely lighter, and faster than
bash. It is different, but what you get is time-saved because tweaking and configuring fish as per your taste isn’t a hassle. The few packages you may ever require, can be fetched using the “oh-my-fish” framework.
To give fish a spin, just do a pacman/brew install fish. Ubuntu requires you to add their ppa, which you can find from https://fishshell.com.
fish does by default what zsh requires you to configure. As the design document kind of bluntly puts it,
Every configuration option in a program is a place where the program is too stupid to figure out for itself what the user really wants, and should be considered a failure of both the program and the programmer who implemented it.
Kneejerk reaction to Ubuntu moseying on towards
systemd for its init. Kind of silly, looking back. Why I stick with it now is because of its automated installer compared to Arch and its decent performance (<1min from cold boot to password entry to XFCE).
Bullshit Jobs by David Graeber. Still going through it, but it nicely sheds some light on my nagging feeling that a lot of work being done every day is just a waste of time.
I loved Debt; one of my favourite non-fiction books of all times. I haven’t read Bullshit Jobs (well I read the article that inspired the book) but I’ve heard good things.
Actually started that just two days ago. My partner had read it I think last year and generally liked it, though she said to feel free to skip ahead at times, as he seems to dwell quite a lot on some points.
Imagined Communities: Reflections on the Origin and Spread of Nationalism by Benedict Anderson
Setting up a cloud-based VPN for the family.
you mean 3rd parties like NordVPN or your own VPN setup. Just curious as I haven’t done the latter part yet. Hoping to know how to do it.