There’s truly nothing more liberating than deleting all of your work by mistake (or having it deleted). That’s why it never hurts to have multiple distribution (and backup) strategies. A newer way is invented every day:

gcc -o delete-this-file.c

Why dabble with Firefox? Everything is customizable. How long will this be so? Who knows. E.g, I have custom stylesheets that hide comments everywhere (Firefox/Chrome) among other things. “Experts” only?

about:debugging#/runtime/this-firefox

chrome://browser/content/browser.xhtml

toolkit.legacyUserProfileCustomizations.stylesheets true

How hard is it to run Linux? It depends on your luck and persistence. I received a junked Lenovo 11e Chromebook recently and it would always freeze at 99% during any distribution install (classic). Enabling a kernel parameter fixed it. How did I know this? Don’t even ask.

#define SDHCI_QUIRK_BROKEN_CQE (1<<17)
(1<<17) = 0x20000

sdhci.debug_quirks=0x20000

I was shown this thing called SSI. It’s the sneakiest of tricks for primitively boosting any SSG. It’s supported in the web servers nginx, apache, lighttpd, and others.

server {
  ssi on;
  ssi_last_modified on;
}

There’s a quick way to test the offline behaviour of programs on Linux.

unshare -c -n bash

$ ip addr
1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

$ lsns -t net
NS  TYPE NPROCS PID   USER  NETNSID    COMMAND
999 net  2      111   user  3          systemd
888 net  1      222   user  unassigned └─bash

I came across a peculiar site. It’s called https://no-color.org (terminals). Xterm and ansifilter work well for programs that are unable to contextually disable colors.

ls -la | ansifilter   # Remove colors from output
xterm -cm             # Set color mode to false
export NO_COLOR=true  # For programs that follow

I used to wonder why some preferred no syntax/color highlighting. It turns out that output can/will be hidden (e.g black on black, white on white) and color contrasts/distinctions are the ultimate talk past.

The interest in TUIs online is high. In the real world you tend to be constrained and blindfolded by the tools available/allowed. Filtering is peculiar though.

See how the terminal/editor splits? Filtering makes them kiss? Commands that input|output (pipe) work best (compilers, transpilers and code generators). The meta is the limit.

Some of my configuration files are online aren’t they? Raku is one of the most interesting, if not the most. I’m not an expert but it pretty much has every language construct (e.g promises) plus exotic stuff. The exotic operators are strangely intuitive (and “hyped”).

my @bin = 1..3;
@bin>>++;
say @bin;

I use it for quick CLIs with the multi dispatch CLI feature. The logo is a butterfly (or maybe it’s a raccoon).

File name, spelling, and dictionary completion exist too. This is tortured, but combining them makes a meta point? The “meta” is hard to convey, but completion doubles as a way of finding, changing, and passing keywords around. Terminals are fair game too. That’s basic completion in a nutshell (minus the magic).

Command line completion is probably another lesser known one. The command line window is minimized, but typing q: (commands) and q/ or q? (search forward/backward) opens it up completely. Wild mode configures its behaviour.