Reid Thompson wrote:
On Thu, 2012-01-12 at 12:07 -0600, sc wrote:
so there might be a faster engine for our scripts
:) heh lets embed tcc and write them all in C
Make lisp the default script engine and import emacs! :O
Look, whenever someone likes a tool, they'd like it used everywhere.
Its the "everything looks like a nail because I have a hammer!"
syndrome. I've seen this with "why learn [some-language: C Java C++
Perl], I think [Fortran|Cobol|Ada] is fine and dandy and should be used
everywhere". In the present case, substitute {some-language=VimL} and
put Favorite-Other-Scripting-Language in [Fortran|...]'s place.
Points in VimL's favor include: current plugins,
backwards-compatibility, know how to use vim you know how to write much
of vimL.
Against: insular
Points in My-Favorite-Other-Scripting-Language's favor as default:
(please include JavaScript, Perl, Ruby, even lisp, etc) has a dedicated
fan base, those who know it don't need to learn something else,
naturally all the other Favorite-Scripting-Languages (including VimL)
are obviously inferior, we can throw out all the current plugins and
rewrite them in a nifty new Favorite-Other-Scripting-Language, if
compilable then faster
Points against: need to include FOSL with vim, knowing Vim doesn't aid
in knowing FOSL, not backwards compatible, need to throw out current
plugin base (unless one is intending to bloat things by keeping VimL, too)
Look: the computing world has become a very-multi-language environment.
Wishing that the One-True-FOSL be supreme is wasteful of wishes.
The current approach lets one bring in several popular FOSLs via an
interface but doesn't require their presence; I think that's the best
possible compromise.
Regards,
Chip Campbell
--
You received this message from the "vim_use" 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
