I don’t think engineers need encouragement to be cynical. More often engineers need to lighten up.

You got a source for that last sentence? I’m inclined to degree, but I’d love to see a a concrete explanation proving it.

Biggest con of KDE + Krohnkite (to me) is no text-based config. I really have no desire to pour through the GUI to set up all my keybinds. I’ve tried this setup before, and honestly I mostly like it. However anytime I want to change something I just hate having to click through a menu with my mouse. The search bar helps, but often you’ll spend a lot of time guessing what the devs decided to name a setting. I went back to Sway and have no regrets. Though I’ll admit I wish there was something that was basically Sway with the benefits you mentioned here.

The IEEE standard actually does not dictate a rounding policy

kitty. The ssh kitten is enough reason to use it. I work ob a lot of different systems that require OTP. Using the ssh kitten I can type the OTP once and can spawn new terminals that ssh and cd to the remote direvtory without logging in again. Obviosly the tabs and window panes are are a must too. There’s tons of other useful features that I like, like using hints to select nunbers, filenames, urls, etc in the terminal output.

with kitty you can open a new terminal session that sets it’s cwd to the remote directory of the server you’re ssh’d into. Honestly the only thing I can think of that termux can do that kitty can’t is saving sessions

I would argue that it is better to have two separate drives for the installation. It simplifies things for non tech savvy people, and I believe Windows has less of an opportunity to mess with your linux install, such as messing with the efi partition.