One series I haven’t seen recommended yet is Alastair Reynolds novels. Revelation Space is a wonderful series, and if you want to start with a standalone story House of Suns and Diamond Dogs are great choices.

For lighter reading there’s also the Murderbot Diaries by Martha Wells.

There’s other older series that may appeal to you: Vatta’s War and Vorkosigan Saga conf to mind.

Consistency with their previous default desktop environment, Unity.

Arch: I need reproducible setups. Also bleeding edge is not for me.

I have to give credit to their documentation though!

What put me off selinux is that the officially documented way of generating a new policy is to run a service unconfined, and then generating the policy from its behaviour. This is backwards on so many levels… In contrast policy-based admission control in kubernetes is a delight to use, and creating new policies is actually doable outside of a lab.

so what are the reasons why it’s a bad daily driver?

Don’t need to go any further than “default user is root.”

Stör is German for sturgeon. And it happens to sound like a lot of other words. Stör Wars, stört your engines, etc. The admins let it run for a while and then put a ban on Stör memes, so everything quieted down. Until this week, when c/risa got the Morn/Gorn/Rom bug.

“Drink verification can…”

In that case gpaste (if you use Gnome). Before that parcellite was my preference, but around the transition to Wayland things broke for me.

Literally copied and pasted that from the article.

I am someone with kubernetes in my job title. If you as a developer are expected to know about kubernetes beyond containerizing your application then your company has set itself up for failure. As you aptly said kubernetes is an ecosystem, and the dev portion is a small niche of that.

You can’t run vmalert without flags

Running grep without parameters is also pretty fucking useless.

500 words in to the over 3,000 word dump, I gave up.

Claims to have a Unix background, doesn’t RTFM.

Nobody really uses Kubernetes for day-to-day work, and it shows. Where UNIX concepts like files and pipes exist from OS internals up to interaction by actual people, cloud-native tooling feels like it’s meant for bureaucrats in well-paid jobs.

Translation: Author does not understand APIs.

Want an asynchronous, hierarchical, recursive, key-value database? With metadata like modified times and access control built-in? Sounds pretty fancy! Files and directories.

Ok. Now give me high availability, atomic writes to sets of keys, caching, access control…

I’m ashamed enough that I can’t really apply to these jobs

This reads as “I applied to the jobs and got rejected. There’s nothing wrong with me, so the jobs must be broken”.

Selection buffer.

Unless you mean clipboard manager, in which case it’ll depend on your desktop environment.