So compared to plain bash without autocomplete and Ctrl+R it may be useful. It is probably a step back for everyone else.

I think it could be much worse than even a plain shell with ^R, as the llm will be slower than the normal history search and probably has less context than the $HISTFILE.

I recently spent some time optimizing a small Julia program I wrote that generates a lookup table of brainfuck constants. Because it only needs to run once, I originally didn’t care about performance when I originally wrote it (and the optimization was mostly for fun).

I achieved an ~100x improvement by adding types, using static arrays and memoization. In the end, the performance was mostly limited by primitive math operations, I tried using multiple threads, but any synchronization destroyed the performance.

However, the most impressive thing was the ability of Julia to scale from dynamically typed scripting language to almost a compiled language with minimal changes to the code.

I agree that having some glyphs in color can be bad, for example when you are typesetting a formula in TeX that contains emoji, the color looks just unprofessional. As a solution, let me introduce you to the Noto Emoji font: https://fonts.google.com/noto/specimen/Noto+Emoji

These shortcuts aren’t provided by the terminal or the shell but the readline library (or zle if you use zsh), which can be configured using the ~/.inputrc file.

I don’t know of one, but why not install gnome on Mint (or Debian)?

I exclusively use podman instead of docker at work and at home and haven’t encountered any unsolvable problems.

Keeping the details about vim in the extras is what I would do as well, but I would definitely tell the students that vim and vi exist, because they are the only editors available on many systems.

I would consider that ifconfig is deprecated on many distros and would therefore teach about iproute2 (mostly the ip and ss commands) instead. Additionally I would consider editing files essential, even if it is with nano.

Maybe mention more modern and simpler help tools like tldr, as they could be even more useful to beginners.

To introduce the shell and utilities, I would try to find a somewhat realistic use case that combines multiple aspects, like analyzing some files or spellchecking instead of simply mentioning every feature one by one.

Thanks, i hadn’t heard oft Factor before, it looks interesting. I’m more of a LISP and FP Person but always wanted to properly learn a stack based language, Factor seems like a nice alternative to Forth for that purpose.

I find that S-expressions are the best syntax for programming languages. And in general infix operators are inferior to either prefix or postfix notation.

Why not write your own version? Getting the temperatures is easy and portable with the sensors command from lm-sensors. The rest of the info is easy to get using various commands (e.g. uptime, free) combined with a bit of sed/grep/awk for formatting.