I take my shitposts very seriously.
It follows the same convention as most programming languages that expose the argument list. Python’s sys.argv has the program name at index 0 and the first argument at index 1. C’s char **argv does the same: index 0 is the program name, index 1 is the first argument. So it stands to reason that Zsh’s $0 should be the program name and $1 should be the first argument…
…which, by the way, is exactly what Bash does as well.
One day time-out. Both of you. If you want to toss shit at each other, take it to Twitter.
That isn’t incorrect, but it’s not as important as people make it out to be. Linux isn’t certified as POSIX-conformant either.
People are way too stuck on POSIX regarding Fish specifically, but in shell scripting, POSIX compliance boils down to “can it run a pure sh script”. Bash is compliant. Zsh is partially compliant and needs to set an option to emulate sh. Fish uses a different syntax and is not compliant; if that is a problem, don’t execute sh scripts in Fish.
POSIX compliance for shell scripts was important in the 80s and 90s when the #! directive wasn’t as commonly implemented and every script might be executed by the user’s $SHELL instead. That is no longer the case as virtually every Unix-like system’s program loader supports #!.
It’s every person’s responsibility to make sure their mom’s (or dad’s (or other parental figure’s)) vibrator runs only secure, trusted software!
My heart bleeds for you, you poor oppressed victim of systemic injustice.
I locked the other thread because this is not a community for politics, nor for airing out your issues with certain people. Those topics are specifically not allowed, and you would know that if you had read the rules. I’ve previously allowed such discussions to go on, in the vain hope that everybody would behave like cultured humans, but eventually they all devolved into exchanges of insults and accusations.
This does not mean that I’m supporting or protecting those individuals. I’m just trying my pathetic best to keep the community clean. If you have an opinion that you must absolutely share with the world, find a community that allows it.
I mean… that’s not incorrect, but…
>>> len("apt update && apt upgrade")
25
>>> len("pacman -Syu")
11
None of the issues you’ve described are Cargo’s fault. The long compilation time is simply rustc’s compile-time checks (ensuring type and memory safety is much more involved than lexing in GCC), and the number of dependencies to compile is a result of the crate ecosystem. Cargo is just the front-end that automates fetching dependencies and compilation with rustc. Blaming it for slow compilation is like hitting your monitor when the computer is acting up.
It’s called a hyperbole.
(edit) But, honestly, it’s still kind of accurate. Many of the most significant software suites that define the Linux ecosystem in more recent decades were written in the 80s or earlier. X (the display protocol) was released in 1984, and X11 in 1987. GNU Emacs was released in 1985. Vi, in 1976. UNIX System V, from which sysvinit and compatible init systems were adopted, was released in 1983. It’s not a stretch to say that certain people want to regress to the 1980s state, even if the kernel wasn’t around.
Off the top of my head, in no particular order:
Most (though not all) of the popular complaints are completely unreasonable. Those people usually see themselves as moral and righteous and expect the world at large to follow their personal creed. I especially consider the UNIX philosophy to be outdated, and strict adherence to it to be an obstacle for modern apps and systems.
I have some issues with systemd, and I don’t like that one for-profit company has such a massive influence over the entire Linux ecosystem, but I have to acknowledge that it works, it works well enough to counter my personal issues, and that the people whose opinion matters the most (specifically Debian and Arch maintainers) chose it for a good reason.
Both harmonicas and bagpipes produce sound by passing air over one or multiple reeds (tuned to resonate at specific fundamental frequencies), inducing oscillations in the reeds, which modulate the air flow. Bagpipes use pipes to amplify the sound, and harmonicas use the cavity between the reed plate and the body, and often the player’s hand.
A digital keyboard that doesn’t produce sound is just a fancy human interface device.
“Shell scripting (various languages, both POSIX-conformant and nonconformant)”
You need to pad that CV with meaningless acronyms!
At the end of the day, every instrument is just a mechanical-to-acoustic transducer with a resonating body to selectively amplify the desired notes and harmonics. The real question is whether a jackdaw qualifies as a sandwich.
Magnus the Red when Emps told him to sit on his crimson ass and do nothing:
The technique is called steganography, and the product is called stegomalware. The payload is concealed as part of some legitimate file, like the pixel data of an image file. It requires the reader software on the targeted system to already be infected, or to have a vulnerability that the payload can exploit.
Low Level video: https://www.youtube.com/watch?v=89ysXVYH2Sk (one more reason to hate Webp)
Quick example by John Hammond: https://www.youtube.com/watch?v=JBIbL8zwZOs
Because someone in the 1970s-80s (who is smarter than we are) decided that single-user mode files should be located in the root and multi-user files should be located in /usr. Somebody else (who is also smarter than we are) decided that it was a stupid ass solution because most of those files are identical and it’s easier to just symlink them to the multi-user directories (because nobody runs single-user systems anymore) than making sure that every search path contains the correct versions of the files, while also preserving backwards compatibility with systems that expect to run in single-user mode. Some distros, like Debian, also have separate executables for unprivileged sessions (/bin and /usr/bin) and privileged sessions (i.e. root, /sbin and /usr/sbin). Other distros, like Arch, symlink all of those directories to /usr/bin to preserve compatibility with programs that refer to executables using full paths.
But for most of us young whippersnappers, the most important reason is that it’s always been done like this, and changing it now would make a lot of developers and admins very unhappy, and lots of software very broken.
The only thing better than perfect is standardized.
OMZ is overrated. It’s too much code for too little effect when most of the plugins boil down to aliases and prompt themes, and all you have to do is source them in your .zshrc anyway.
I am by no means saying that the plugins and themes are useless. I’m saying that OMZ is unnecessary.
“Everything is a file” means that many of the system’s components are represented as abstractions in the filesystem. It’s simply an API that allows reading from and writing to it by integrating into the hierarchical file structure.
If you take a look inside
/sys, you will find a fuckton of files, but they don’t represent data stored on a mass storage medium. Instead, the directory contains a mountedsysfsfilesystem that contains file-like representations of various parts and properties of the system. For example, you can read them like a file by runningcat /sys/block/sda/queue/rotationalto check if thesdablock device is a spinning disk (1) or solid-state storage (0). Or you can write to them like a file by runningecho 1 > /sys/block/sda/devices/deleteto commandsda’s driver to detach the device. Similarly,/proccontains a mountedprocfsfilesystem that presents information about running processes as file-like entries;/devcontains a mounteddevfsthat points to various devices; and/tmpand/runcontaintmpfsmounts for temporary storage in volatile memory (RAM or swap).Windows uses various other APIs (like the Component Object Model and others) to accomplish the same that are not necessarily tied into the filesystem.