Porn, Zen, and .vimrc

Good read. My strategy for avoiding all the vim porn and "plugin-madness" is to never install a plugin or mapping/override without learning to do the thing manually in vanilla vim. This way you'll KNOW if that plugin is really worth the bloat, and if you do end up away from your config on a remote server you're just mildly uncomfortable instead of dead in the water.

Re: Porn, Zen, and .vimrc

#7

Post by d10y3vh5 » Fri, Oct 16, 2020, 11:18 PM UTC

> This article describes my Vim journey, starting from heavy personal customization and ending with a renewed love for defaults

this exact pattern is found in so many vi|m articles and is touted as a triumph of vim's default patterns, when it is really a failure of vim to support whole ranges of functionality. as a daily user of neovim, i know that vscode is a superior alternative and am waiting for a month off to transfer all my vim customizations to a real ide

Re: Porn, Zen, and .vimrc

#8

Post by xwdv » Fri, Oct 16, 2020, 11:20 PM UTC

d10y3vh5 wrote: post #7

> This article describes my Vim journey, starting from heavy personal customization and ending with a renewed love for defaults this exact pattern is found in so many vi|m articles and is touted as a triumph of vim's default patterns, when it is really a failure of vim to support whole ranges of functionality. as a daily user of neovim, i know that vscode is a superior alternative and am waiting for a month off to tr…

It is not superior, you just have not reached enlightenment.

Re: Porn, Zen, and .vimrc

#9

Post by smoyer » Fri, Oct 16, 2020, 11:29 PM UTC

d10y3vh5 wrote: post #7

> This article describes my Vim journey, starting from heavy personal customization and ending with a renewed love for defaults this exact pattern is found in so many vi|m articles and is touted as a triumph of vim's default patterns, when it is really a failure of vim to support whole ranges of functionality. as a daily user of neovim, i know that vscode is a superior alternative and am waiting for a month off to tr…

This pattern is also seen in almost every enterprise application purchase I've seen over the last 10-15 years. The process is as follows:

1) RFP, RFQ then purchase your ideal enterprise application.

2) Start customizing it to meet your old way of working (and before you really understand it) while ignoring the fact that X's 10000 customers seem to do fine with the default configuration.

3) Complain that it won't really let you work the way you did a) on the mainframe which was designed based on b) the way you did it with paper and pen.

4) Throw in the towel or force your users to adopt some practice that was neither a) your original process or b) the vendors optimized process.

I've seen this pattern with:

1) Oracle ERP

2) SAP

3) Jira (twice)

4) PeopleSoft (twice)

5) Workday

6) ServiceNow

7) Remedy (twice)

One of the most solid recommendations I can give is that when you purchase a software system, don't do any customization for the first 12-18 months.

P.S. Okay ... go ahead and put your logo on it.

Re: Porn, Zen, and .vimrc

#10

Post by yoyohello13 » Fri, Oct 16, 2020, 11:39 PM UTC

d10y3vh5 wrote: post #7

> This article describes my Vim journey, starting from heavy personal customization and ending with a renewed love for defaults this exact pattern is found in so many vi|m articles and is touted as a triumph of vim's default patterns, when it is really a failure of vim to support whole ranges of functionality. as a daily user of neovim, i know that vscode is a superior alternative and am waiting for a month off to tr…

emacs is the real ide