On Sat, Dec 28, 2013 at 1:24 PM, Marc Weber <[email protected]> wrote:
> Excerpts from marcelspostbakje's message of Fri Dec 27 11:25:08 +0100 2013: > > Airline is a pure vim-script alternative to powerline and thus is > > lightweight and fast. Also an example why vim-script should not be > > dropped. > Bullshit. Just because something happens to exist which is fast does not > proof that the language is fast enough for many (common?) use cases. > http://vim-wiki.mawercer.de/wiki/topic/in-which-way-does-viml-suck.html > The only reason why it still exists the way it is is because rewriting > (it and plugins) would be so much work. > > The only reason to keep is the amount of code which has been written. > There may be a lot wrong with VimL, but it is always available, not dependent on any other package than Vim itself. That is a big pro. It is capable of a lot of things and it is lightweight. That something exists is no reason, I agree, but lightweight and no external dependencies is what my point was. It would be stupid to drop that. I wasn't really clear about that. VAM does not allow installing older versions because this never was a problem. In fact its a design choice: Less possibilities to combine packages => less maintainance => less trouble. I never used the option to install older revisions, but I don't mind having an option I don't use. Vim is loaded with such options. :) - VAM supports a pool of known packages. Thus if a package is obviously > replaced/outdated/unmaintained there is a way to tell the users. > Thus this reduces questions about "why doesn't my old sander's > snipmate fail with X" on irc. > > That is a nice feature, but as it is limiting the use of unmaintained packages it's not for me. I'll take the risk if I use unmaintained packages. And I still like those to be managed. VAM has definitly an other target group of users. Which is great. Choice is good. > - VAM allows package maintainers to specify dependencies in a package > description, thus installing it by name is enough, no need to declare > dependencies in vimrc. > That is great, but will only work if all packages follow the guidelines. You'll create a high quility repository this way, which is great. But I said before it also limits the number of packages as long as not every plugin developer follows that guideline. > - it allows arbitrary sources, git(hub),svn, etc. > > (Due to mirroring (vim-scriptsn) I agree this is unlikely to be such a big > advantage) > > NeoBundle does too. Copy-paste from the helpfile *neobundle-options-type* type (String) Specify the repository type. If omitted, a guess is made based on {repository}. Available types: "nosync" : No synchronous "raw" : Raw plugin file ("script_type" attribute is needed) "git" : Git "hg" : Mercurial "svn" : Subversion Example: > NeoBundle 'git://host/path/repo.git', {'type': 'hg'} NeoBundle 'thinca/vim-localrc', {'type' : 'svn'} > Anyway I've tried updating the matrix adding most NeoBundle features I > found. If you feel something is missing drop me a note: > http://vim-wiki.mawercer.de/wiki/topic/vim%20plugin%20managment.html > So thanks for telling me. > > So it looks like there is yet another competitive rewrite of plugin > management. > > VAM and NeoBundle have different target users. VAM goes for quality management of the plugins, NeoBundle is for the users who want to have the most options. The lazy loading is my favourite option, works with most plugins out of the box and makes Vim startup fast even with a lot of plugins installed. I think that option deserves to be mentioned. If you don't use the plugin it won't be loaded. It's loaded on demand. I'm not a NeoBundle power user, I just use the features I need. Shougo can tell you a lot more. He wrote it. Thanks for your answer, Marcel Boon -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
