3 ms·

The vim configuration process can be easily automated. I too put .vimrc on any machine I use vim on. The problem is auditing. Do you have time to audit the plug

The vim configuration process can be easily automated. I too put .vimrc on any machine I use vim on. The problem is auditing. Do you have time to audit the plugins you use? Do you keep up to date with their changes(license, policies), or simply run :Vundle update or :Plug update. In vim the configuration process itself is not that cubersome, just that the trust surface is very vast, whereas in IntelliJ I need to trust only one single entity.

chmln 8y ago
You got a point, and this reminds me of the kite debacle with sublime . However, there's a difference. Sublime plugins update automatically startup, while mine are updated manually. If I theoretically wanted to, I could audit the plugins one by one. I'm not sure I would trust jetbrains - it's closed source and I don't know what data they're phoning home, or telemetry. With vim at least I have the possibility to audit. With a closed source product, it's way harder.
nickjj 8y ago
I really like the :Plug model with Vim. Nothing updates unless you do it, but then once the update is done you can optionally go through the commit log of each plugin and even revert back specific commits if you don't like what you see. To me that's a much better model than "hi, I see you opened your code editor, let me auto-update these 10 plugins for you. Hopefully things work out for you!". IMO the user (you) should be in total control over when things get updated. This goes for the editor itself and your OS too. Otherwise you have no idea what the state of your system will be the next day.
milch 8y ago
As a counter point, JetBrains almost certainly uses Open Source libraries in their products. You can say you trust that they've vetted every single version of every library they've ever released and all their transitive dependencies, but the likelihood they've actually done that is slim to none (else it would be item #1 in all their marketing material)

chmln 8y ago

You got a point, and this reminds me of the kite debacle with sublime . However, there's a difference. Sublime plugins update automatically startup, while mine are updated manually. If I theoretically wanted to, I could audit the plugins one by one. I'm not sure I would trust jetbrains - it's closed source and I don't know what data they're phoning home, or telemetry. With vim at least I have the possibility to audit. With a closed source product, it's way harder.

nickjj 8y ago

I really like the :Plug model with Vim. Nothing updates unless you do it, but then once the update is done you can optionally go through the commit log of each plugin and even revert back specific commits if you don't like what you see. To me that's a much better model than "hi, I see you opened your code editor, let me auto-update these 10 plugins for you. Hopefully things work out for you!". IMO the user (you) should be in total control over when things get updated. This goes for the editor itself and your OS too. Otherwise you have no idea what the state of your system will be the next day.

milch 8y ago

As a counter point, JetBrains almost certainly uses Open Source libraries in their products. You can say you trust that they've vetted every single version of every library they've ever released and all their transitive dependencies, but the likelihood they've actually done that is slim to none (else it would be item #1 in all their marketing material)