Return to index | Updated on -0400=2022-10-02T11:59 | This page is compliant HTML 3.2

Software Catalog

This is an index of software I think deserves more exposure. The exposure may be positive or negative. Programming languages are included as well.

Recommended software

External lists

I can't vouch for all the software included in the following links, but their contents are generally interesting.

RI's list

Software Description Screenshot/Logo
uuterm (local, main) Terminal emulator by Rich Felker (musl libc's author). VERY fast, significantly faster than st, but also even more spartan feature-wise. Has X11 and linuxfb support. Make sure to try out the different fonts with the UUTERM_FONT environment variable. Pending
Classic Colors MS Paint for UNIX. Made with the Motif toolkit. Classic Colors screenshot (19K)
FOX Toolkit and related applications Fast C++ toolkit, with a Win95 look. Its most remarkable projects: X File Explorer (Xfe), the Adie text editor, the FOX Calculator, among others. Pending
Amiga software on Unixoids as direct ports or heavily inspired Examples: CYCAS, an architecture CAD; HSC, the oldest static site generator in use today; Grafx2, bitmap paint program inspired by Deluxe Paint and Brilliance Pending
FileRunner Two pane file manager inspired by the Amiga's DirMaster and Directory Opus. FileRunner screenshot (26K)
XRN Usenet News reader for the X window system. Athena-dependent. Pending

Software to avoid


A true death blow: Stroustrup's interview with IEEE in 1998 (13K)

Juicy fact: If you use GNU/Linux, well, both the GNU guy and the Linux guy hate on C++:

GNU guy

C++ is a badly designed and ugly language. It would be a shame to use it in Emacs.

The reason the GCC developers wanted to use it is for destructors and generics. These aren't much use in Emacs, which has GC and in which data types are handled at the Lisp level.

Linux guy

C++ is a horrible language. It's made more horrible by the fact that a lot of substandard programmers use it, to the point where it's much much easier to generate total and utter crap with it. Quite frankly, even if the choice of C were to do nothing but keep the C++ programmers out, that in itself would be a huge reason to use C.

In general, I'd say that anybody who designs his kernel modules for C++ is either

  1. looking for problems
  2. a C++ bigot that can't see what he is writing is really just C anyway
  3. was given an assignment in CS class to do so.

Another thing they don't tell you is how GCC's C++ rewrite made it far slower and use up far more memory.

Without C++, we'd have faster and far lighter compilers, faster compilation times and of course one less disastrous language to cope with.


Watch Rob Pike talk down to Golang users (2955K):

[...] Our programmers are Googlers, they're not researchers. They're typically fairly young, fresh out of school, probably learned Java, maybe learned C or C++, probably learned Python... They're not capable of understanding a brilliant language, but we want to use them to build good software.

Another thing to note is the text in the video's slide:

Software engineering
A personal definition: To maximize the quality of software a given group of programmers can create.

I think Rob Pike meant to evoke Matthew 7:6, do not throw pearls before swine, lest they trample them under their feet, and turn and tear you to pieces.

Drew DeVault made two blog posts ( "Goproxy breaks Go", "Google has been DDoSing Sourcehut"), summarized by Arsenallish:

By default, its package manager connects to Google to proxy everyting. You have to opt out of that spyware to directly connect to the repos. Also, the Google proxy servers DDoS small source places like Sourcehut. On top of that, if you want to contribute to the code, you must make a Google account to sign their contract agreement/CLA/code of conduct with it.

Even if you attempted to fork the language, it would add the obstacle of having users download your Go fork only to compile the program you're working on!

They got us played like a fiddle...


Gentoo Forums: s6/s6-rc vs systemd, or why you probably do not need systemd


It doesn't matter if the protocol is technically better if its ecosystem is unpalatable. You are stuck with i3 and dwm-like clones, and KDE5/GNOME3 are your DE choices. All the older and lighter toolkits of the almost 40-year old X are no more on Wayland.

The "Boycott Wayland" GitHub gist has a lot of valuable information, especially in the comments. A blogpost by Dudemanguy ("Wayland isn't going to save the Linux desktop") details the results of his experiences with Wayland over many years.

Return to index | Updated on -0400=2022-10-02T11:59 | This page is compliant HTML 3.2