The commands available in Unix are developed by users for users. They are not too easy to learn for the reason that they are optimized for full-time users and not for a once every third-month users.

But as noted, they have established a standard that has been ported to just about any environment. It's a bit like POSIX or the C RTL - there is a large and well-oiled common ground always available, quickly getting people up to speed on new platforms.

Most GUI hides important settings in XML files (better) or binary configuration files (disgusting), making it a huge reverse-engineering project to be able to take the backup files from a project and manage to set up a working environment for building binaries.

I don't mind using a GUI, but expects one of the outcomes of the project to be command-line files for building the project binaries outside the GUI. If the GUI has the compiler or linker integrated, then that GUI is uninstalled more or less instantly.

Hardware locks really are evil incarnate - how can a user take backup copies of a hardware lock to make sure that they can reproduce a build environment 10 years from now? How do you fire-protect the hardware lock?