Oh, the things Vim could teach Silicon Valley's code slingers

Re: @Doctor Syntax

But you said it yourself:

"CAN be configured to" as opposed to vim's IS configured to.

Vi out of the box isn't configured to do that, and the user has the choice to do so. Whereas vim is the opposite, it is configured out of the box to hide them. And, unless you know that that is a feature of vim, and in fact if you even know you ARE using vim (most Linux's these days symlink vi to vim, so you could be using vim without realising it - initially at least) then you might not even realise it's not showing things you'd expect it to. That can cause all sorts of trouble.

Re: As a long-time Vim user (since 2005 or so)

"I much prefered EDT and TPU, personally."

I did enjoy using TPU, but the joy was derived from the sense of achievement I got from mastering something awkward. Once I got stuck into Emacs/vi/sed/awk I never looked back. :)

Re: As a long-time Vim user (since 2005 or so)

Heathen!

TECO forever!!!!!

Re: As a long-time Vim user (since 2005 or so)

EDT was my DEC editor of choice. Lighter weight than EDiT. I used ini files for EDiT to make it act like EDT, until conversion to HPUX in 2011 and I had to say goodbye to OpenVMS. I then used VI to relive my days with...

TECO on RT11. That was the cat's meow. Coded an entire financial report system in FORTRAN using a VT52.

Re: As a long-time Vim user (since 2005 or so)

Next thing you know, you'll be praising TECO, and I shall have to call the police.

(This is where we need a "Get off my lawn, young whippersnappers" icon)

Re: As a long-time Vim user (since 2005 or so)

meh, ed is so much better!

Re: Ah - the good old days

Granite? We used to dream about chiseling letters in granite!

We had to scratch them into hot lava with our bare hands!

Re: Ah - the good old days

"Containers are cool, for example, a good progress ... I do not have to write the examples of bad progress, we all know them ...."

To be fair, on a properly configured unix system with decent security settings and appropriately set up

LD_LIBRARY_PATH you wouldn't even need containers. Users and applications could happily operate alongside each other with little issue. In fact back in the day I remember one of my old university HP-UX boxes happily managing to support literally hundreds of users simultaniously just using normal user-group-world permissions and quotas. Containers and VMs in general are really for OS's , ok Windows , whose chinese walls leave something to be desired or where you really need different OS's running but only have 1 box to do it on.

Re: Ah - the good old days

"The Linux world is more and more littered with monolithic enthusiasts, who think "the more this binary can do the better and it is so powerful that it is normal that it be dependent on all this other stuff ... ". Obviously, with bloat come bugs ... we are shifting from screwdriver, wrench, knife, spoon, and fork to Swiss army knives for everything, certainly not something I call advance."

Perfect example, that piece of shit, bat-shit crazy systemd. That should have never have been conceived let alone gotten far enough along to need an abortion. It still baffles me why that's got the legs it has.

Re: Ah - the good old days

George R.R Martin apparently uses WordStar 4.0 to write GoT

Is that an endorsement, or a criticism, though...

Re: Vi and Vim are the spawn of Satan

I use whichever vi clone is on the computer I'm using.

At home, I've been using elvis on Slackware since Slack 0.99 (:version reports "elvis 1.7 by Steve Kirkendall 30 December 1992") ... although I'll admit that I've been using gVim more than elvis-in-an-Xterm on my GUI of choice for over a decade and a half.

Re: Vi and Vim are the spawn of Satan

If you were a nerd, sitting at your own computer, writing to alt.flame, you used emacs.

If you were a highly paid software contractor visiting many *nix equipped sites, you bloody well learned vi, because it was the only editor you could guarantee was on every *nix system.