linuxmemes

I've found that one of the best things to do when making a library for something that is going to have a web interface is to first have it work in the terminal. You can much more quickly play around with the design and fix issues there instead of having to work with a more complex web interface.

You just create a simple menu system, like input("1: Feature A\n2: Feature B\n>") and just start trying out all of the different scenarios and workflows.

It’s wild that Linux stans are such masochists that they believe they can convert people to loving abuse, instead of just making the interface better to attract users.

I use both Windows and Linux. I also mess around with github programs here and there and they almost all require use of a command line to install or manipulate. And because a command line intrinsically is going to inform you way too little or way too much about what you are doing I end up having way more technical issues because I don't realize I'm missing a dependency or I glazed over an error that popped up in a sea of text during installation.

Linux's leaning on CLI is good for extremes: ultra-techy programmers and perfectionists and the exact opposite: people who just want internet and a word processor (who will install like basically nothing anyway so CLI wont bother them and probably keep them from breaking something in a GUI settings page).

People in the middle who are semi-techy end up annoyed because if they want to do some middle of the road changes to their system they have to use a command line or even code something themselves. Instead of just using a search engine to find the 1 out of a billion different little windows based applications that already exist to do the small yet very specific thing to a "good enough" level. Which just requires a minute or two of internet research, clicking download, waiting a bit, then installing a thing. Some of those tasks you can do while doing something else.

Or yes, maybe they end up needing to edit an ini file or a registry file (very rarely in the latter case).

Basically I'm talking about tech users that always use the path of least resistance rather than the most advanced or custom. People who want to do 20% of the work to get 80% of the results.

My favorite example of the use of both are PDFs:

• I'll use Stirling-PDF to insert/replace pages in specific places, rotate, move pages, etc. I like to visually understand what I'm doing.
• I'll use pdfunite to merge PDFs.