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 assume that nothing will change for contributors, as vector tiles only replace the existing renderer.

For users this will allow better zooming and customization of the rendered map.

I personally would not take it out, "unused" RAM will be used by the OS as e.g. disk cache, or you could have a fairly large ramdisk.

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

I don't really have a single favorite a language, if I am able to choose freely it depends on the task.

• C++ for natively compiled programs and C interoperability, I like the types from the STL and templates.
• Clojure is IMO great for data-oriented programs, I really like the immutability and it being a lisp. The java interop and the ability to compile to JavaScript with clojurescript can also be useful.
• Julia for smaller (mostly numerical) programs that should be fast at runtime. The type system is great in being optional, but strong and significantly improving performance when types annotations are used.
• Fennel (or Lua) is definitely my favorite Language for embedding into larger programs and scripting. Fennel has the advantage of being a lisp and cleanly compiling to lua.
• brainf*ck is great as a simple language to have fun and enjoy programming

RAID 5/6 is somewhat broken, and some people might consider the lack of built in encryption or support for a cache disk as problems. For some reason it seems popular to blame it for data loss.

That being said, it is my favorite file system and I never had problems with data loss, but I use ECC RAM on my desktop as is strongly recommended if you use btrfs or zfs (another potential downside).

I genuinely don't know if scratch is the right choice or a simple text based language would be better, especially for the older kids. Just from my personal experience, I started programming in BASIC at 12 and don't think I would have had as much fun and continued programming if i had used scratch instead.

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 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.

I find it interesting how large the difference between tastes regarding music players is. After the development of Cantata ceased, I was unable to find any mpd client that I liked and decided to write my own instead (if anyone is interested, the code is available at https://github.com/dokutan/cmpdc)

Of course anecdotes are of very limited usefulness, but I had exactly the opposite experience. The HDDs that failed on me, failed slowly with SMART errors that gave enough time to make a backup, and never failed completely. On the other hand I had a cheap SSD die completely and without any warning after only limited use, and experienced bit rot even on reputable vendors.

tl;dr choose what you want but make backups