kellyjprice

Is typing 10 lines of code your bottleneck?

I'm not trying to discount it the analogy, but I'd much rather live without cars (or a lot less).

Would you consider lobster or crab, bugs?

Probably. I have not had any problems switching between the two. It's meant to be a drop in replacement, but I'm not sure how perfect that is.

If you're at all interested in tiling window managers, I can't recommend regolith enough. It's built on top a minimal ubuntu install and gnome-settings-daemon, so it gives you most of the non-window manager desktop stuff you would expect. At first, the distro was all the same stuff I would uninstall/install to roll my own environment. But they keep working on it and expanding the docs.

The only difficult part for me, is that they change the i3 config defaults. So often, instead of checking the i3 docs, I have to read my local config first.

> ...where it makes sense to do so.

Certainly being able to trace code is one skill, and knowing how deep to go is another.

I think you're ignoring the additional complexity added by the fermentation. It's not fair to compare juice to a fermented juice. As I understand it, it is objectively more special than other fruit juices.

That's a habit I may never break. There's been enough times that vi was actually vi.

All the time, at least twice already today. Another common command that I'll start typing only to switch context from is vim.

What happened to the time when KDE was respected as a beautiful DE?

I can think of 2 much older examples of 'kit', as a part of toolkit, in a UI framework name:

* GTK

* Tk of Perl/Tk