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

Think about all the keystrokes you'd save if you just typed "vi" instead.

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

What kind of evil system ships with both vi and vim?

OpenBSD comes standard with vi. Vim is a package.

It ships nvi, as do the other BSDs. I think it's reasonable, BSDs have a stronger divide between the base system and third party packages, I'm not sure it would make a lot of sense to maintain vim as part of the former.

Besides on my FreeBSD system /usr/bin/vi is around 400kB while on my Debian machine /usr/bin/vim.basic is 2.4MB. It's not much these days but on embedded platform it could still make a significant difference.

Yep, and "nex/nvi are intended as bug-for-bug compatible replacements for the original Fourth Berkeley Software Distribution (4BSD) ex and vi programs."

Debian is the same way. But as soon as you open a file with vi on a fresh install, you know it isn't vim, so you close the editor, install vim, and then the vi command opens vim.

I had heard that recitations of the Odyssey were more improvisational. If I remember the gist correctly, someone proposed that adjectives, for instance, were chosen to match the meter of a particular line.

https://en.wikipedia.org/wiki/Oral-formulaic_composition

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

It's still the most popular. Check any polls.

KDE 4 happened

To be fair KDE4 _was_ a disaster when it was released but in time it came to be as stable and usable as the much loved KDE3. The path to plasma was also somewhat rocky (but nowhere near as bad as the KDE3 - KDE4 transition).

I used to enjoy using KDE but I feel they lost their way and are overly attracted by "shiny new things" like workspaces, activities, or semantic desktop - virtually everything being dependent on strigi then akonadi then nepomuk then baloo or ... The real bugbear is that every time they ditch everything for a new metaphor - so much of the previously working and reliable software is also ditched or obsolete.

It doesn't suit my needs to have to keep re-configuring my computer and software and workflow so I stopped using it.

I do think it's great and valuable that it's there as an option though.

Akonadi was the main reason why I ditched KMail for Thunderbird six years ago. I recently went back, and it's marginally better. But it's still pretty outrageous that a service that only gives one user-visible extra feature (mail checking and calendar reminders as a background service) costs 330 megabytes of RAM. Most of that for the MySQL instance that it's using; no idea why they have to use anything else than SQLite for a mailbox with maybe 100 mails. Stopping Akonadi is a thing that I just have to do before launching Minecraft on my notebook.

  $ free; akonadictl stop; sleep 15; free
                total        used        free      shared  buff/cache   available
  Mem:        3934720     1227872     1296492      253868     1410356     2203068
  Swap:             0           0           0
                total        used        free      shared  buff/cache   available
  Mem:        3934720      897308     1626924      249452     1410488     2538072
  Swap:             0           0           0

I'm still sticking with KMail for now, though. The UI is a bit nicer (esp. w.r.t. GPG), and mail checking as a background service is nice.

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

NeXTSTEP (macOS and iOS's predecessor) predates Tk's the use of the term kit by 3 years and GTK's by almost 10.

I believe I get less lag in xterm within an Ubuntu VM than with iTerm2.

I've been using it casually as my /home for ~2 years. The most stress it gets is torrenting movies to it. But, there's been no problems. Setting it up on 3 drives was dead simple.

*per month.