You can start by moving your development workflows (pull requests, issue tracking, etc.) to something like codeberg. You can continue publishing your PyPI package from Github by just pushing your code from codeberg to Github.

Eventually you can also move the publishing pipeline over as well. I don’t know how complicated your library is, of course, but in simplest cases it’s a matter of rewriting a config file in a slightly different way.

I think it depends a lot on what kind of application you’re thinking of. Here are some examples of tools that I particularly remember for having nice CLI interfaces, but they are all slightly different in terms of the number of operations/entities they support.

Single operation, a lot of different types of data: httpie

httpie is a CLI HTTP client. It allows to generate fairly complex requests, choose which diagnostic information you want to see, etc.

Examples:

$ https httpie.io/hello
$ http PUT pie.dev/put X-API-Token:123 name=John
$ http -v pie.dev/get

Several operations, a lot of parameters: Bazel

Bazel is a build system. There are only a handful of operations you typically perform (build, run, test, query), but they all follow the same pattern.

Examples:

$ bazel build //app
$ bazel --quiet build //app -c opt
$ bazel --quiet run //app -c opt -- --port=1234

Multiple entites, multiple operations: LVM

I really liked the interface of Linux Volume Manager tools. They consist of multiple commands that follow the same pattern, and use the same flags for options.

Examples:

# vgcreate -n vg_name
# vgs
# pvcreate /dev/sda
# vgextend vg_name /dev/sda
# lvcreate vg_name -n lv_name -L5G
# lvresize vg_name/lv_name -L+1G
# lvs

Wanted to mention jj too. It follows a fairly standard pattern of ‘<command> <noun> <verb>’, e.g. ‘jj bookmark create’, allows to abbreviate unambiguous commands (e.g. ‘jj b c’), has a lot of QoL features (such as highlighting unique prefixes of change IDs in the output). Really a lot of thought went into CLI design specifically it seems.

Thank you for the correction! Appreciate your integrity.

I call bullshit on that. Wikipedia says compulsory voting ended in 1993: https://en.wikipedia.org/wiki/Compulsory_voting

Pretty sure I saw some. In Tierpark Schönbrunn.

I wouldn’t say that compulsory voting is “stupid”. There are some very good arguments for it.

Firstly, it addresses the imbalance of cost of voting (the time and effort you need to spend to cast your vote) with its effect (the tiny fraction of impact your vote has on the outcome). This disproportionately affects lower income voters, especially in some countries like the US, where voting usually happens on a weekday.

Secondly, the outcomes are no longer won “by turnout”. In other words, to win the election you can no longer merely convince your supporters to vote for you, you need to actually convince people who don’t support you to vote for you.

Thirdly, and perhaps less convincingly, this stimulates the interest in the decision and the outcome. Since you have to vote, you may be inclined to actually form your opinion about the elections, and follow up on its outcomes.

Go to Preferences -> Audio -> Replay Gain mode and set it to “Album” (if you’re listening to whole albums) or “Track” (if you’re mixing it up). This will let VLC read the ReplayGain[1] tags in your files and adjust playback volume accordingly. Chances are high that a lot of your collection already has these tags, and you won’t have to do anything else. If some of your files don’t have these tags, just run a tool (https://github.com/complexlogic/rsgain for example) to generate them.