Erez Schatz

Authored Comments

It's like opensource.com spend a year building up a reputation for being a serious, well researched site for serious, well-researched linux content, then blow it up with this joke, lazy poll where they copy/paste the top 15 names from Distrowatch and don't even take a second look. At least if they would call it "what is your preferred name from this copy-pasted list".

The result is the inclusion of general-use distro like Debian and Arch, not to mention CentOS - a server-oriented Distro, and of course, React OS.

At least last year sad joke inclusion was a FreeBSD derivative. This year it's a re-implementation of WINDOWS NT.

WINDOWS NT.

WINDOWS.

NT.

See ya next year!

"While "vim" is the technically correct name of the newer version of the vi editor, this article refers to it as "vi."."

It's not "the technically correct", it's the actual program. What you're using isn't vi, it's vim. It's a different program, with different code, with different capabilities, who's basic premise is that, with specific flags, it's vi-compatible. It's no more vi than Linux is UNIX or than your car is a Ford Model T. In fact, the "vi" program used in many distros is actually vim compiled and ran to be as vi-compatible as possible.

And the main reason for all this is that vi was non-extendable. Therefore you can't turn "your vi editor" into anything, because the vi editor does not support configurations, scripting, modules, themes or anything like what is described here.