Yes. And many people here doesn’t seem to get that.

I’m not a dev of any kind. I occasionally write some bash and awk scriots to automate some things and if I need some kind of plain text (non-binary) data format I prefer tsv over json.

So why do I still get this? Is it just that many json advocates want to make sure others know json does support other data types than plain string?

There’s no any kind of announcement that pfetch is no longer maintained. My guess is: “it’s ready”.

EDIT: Looks like Dylan has been “offline” for some time…

Holy unholiness, Batman!

I did expect those kinds of tricks would cause syntax error in #defines, but instead looks like everything is allowed… Some day someone #defines a such abomination that it creates universe wide black hole -like vacuum and everything ceases to exist.

I’m not a C programmer (is this code even C?), but I anticipated seeing comments like this. 😂

Hehe.

I see what you did there.

… wait?

Used for scripting, but not recommended to be used in scripting?

$array actually expands to every element in an array.

Very convenient. But ~every shell script is written in bash or POSIX(y) sh. When I need to write shell scripts I begin with busybox sh compability. If it turns out to be too complex, I’ll convert to bash. This is because if I ever would publish the script it would have better changes to be accepted as a PR for example. Yes. Bash is a mess. I don’t even like it that much. It’s okay. But it’s more standard then zsh. Although I’ve seen the tides turn on some occasions, like macOS.

Maybe some day I’ll give zsh a second chance.

Webkit and Chromium tend to take even longer.