Even when you don't know the language, you can judge if something is an ad just by an overly excited tone of voice. I wonder if someone has tried writing an ad detection algorithm already. It would still be a lot heavier on resources than SponsorBlock.
I am writing #!/usr/bin/env sh for dead simple scripts, so they will be a tiny bit more portable and run a tiny bit faster. The lack of arrays causes too much pain in longer scripts. I would love to use Fish, but it lacks a strict mode.
No, why would I?
I used to share all my dotfiles, scripts included, but I was too afraid that I would publish some secrets someday, so I stopped doing that. For synchronizing commands, aliases and other stuff between computers I use Chezmoi.
To use Fish instead of fighting with start up time of Zsh with hundreds of plugins
Always use the so-called "strict mode" in Bash, that is, the set -euo pipefail line. It will make Bash error on non-zero exit code, undefined variables and non-zero exit codes in commands in pipe. Also, always use shellcheck. It's extremely easy to make a mistake in Bash. If you want to check the single command exit code manually, just wrap it in set +e and set -e.
Consider writing your scripts in Python. Like Bash, it also has some warts, but is multiplatform and easy to read. I have a snippet which contains some boilerplate like a main function definition with ArgumentParser instantiated. Then at the end of the script the main function is called wrapped in try … except KeyboardInterrupt: exit(130) which should be a default behavior.
Absolutely not a bad practice. If you need to use them on a remote server and can't remember what they stand for, you can always execute type some_command. Oh, and read about abbreviations in Fish. It always expands the abbreviation, so you see what you execute.
I don't have the "Used space" column, probably because I have quota disabled. I managed to find out using btdu, that the snapshot 1137 takes ~8.3 GiB.
I cannot delete it using that command, because it is marked with "+" which means it is the "btrfs default subvolume", according to snapper manual. I wonder if there is still a way to get rid of it.
No, I think they meant that you get better resource usage when you install an app as a Flatpak instead of a system package. You get the same benefit in a traditional distro too, if you use Flatpaks, it's just that immutable distros kind of force you to use them.
Well, I wouldn't really say that it's used as a Windows replacement at the company I'm working at, because all the business stuff is still being done using Windows, but almost all developers are using Linux. I was even allowed to replace Ubuntu with Arch, because I was annoyed by outdated packages. Because of the higher freedom, I can even tolerate the slightly smaller pay rate and benefits that I could earn elsewhere.
You have entrance lanes on the left‽ 😳