> 1. Drop support for anything except Python (including vimscript) >Reason: >Take it from me, nobody wants to start using an editor & wants to know that, >due to some compile time events, they can't use this plugin. I wanted to >install Command-T plugin & came to know that, I can't install it, because I >don't have +ruby in my vim. It sucks. >Dropping Vimscript support may be the toughest job, but think of it. Do you >feel in your heart that, there's anyone on earth, who honestly want to program >in vimscript? Is there anything, that can be done in vimscript, but can't be >done in python? By loosing vimscript, you will be losing many years of plugin >development. But look at the bright side. I feel a little bit frustrated, when >I see the plugin I am going to use, was last developed 3 years before(Though >it works better than anything else I have used). Losing vimscript, you are >bringing a revolution in development. If you are thinking no plugin will be >developed, take a look at sublime text & see how fast it has caught up with >emacs & vim.
Vim must not drop support of Vim script. Because, Vim must have backward compatiblities. If Vim drop it, Vim will be not Vim(it is Vim like another editor). And the suggestion is too hard work. If Vim supports another default script language, I think Lua is better. Yes, Python is good language and has good libraries. But it is too huge as default built-in language. Lua is small, fast, and available most of architectures. So the "I think xxx is better default script language than VimL" is like the editor war. -- -- 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.
