• thingsiplay@beehaw.org
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    1 year ago

    Vim: Clearly evil, lightning fast. Relies on vimscript for any interactivity and can barely be used outside of the editor.

    I don’t know why you want use Vimscript for anything outside of the editor. But if that your issue, then there is Neovim. It uses Lua instead Vimscript, but what is the benefit of using Lua outside of Vim? That changes nothing.

    • cygnus@lemmy.ca
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      It uses Lua instead Vimscript, but what is the benefit of using Lua outside of Vim?

      The only other (in fact, the first) place I’ve run into Lua is WoW plugins.

    • tetris11@lemmy.ml
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      1 year ago

      Lua outside of Vim has huge applications in embedded products. Dude I would kill for Lua. Do you know what we have? Common Lisp. Yeah, it’s great and fancy and all, but try adding that to your CV and applying for an embedded system job.

      • thingsiplay@beehaw.org
        link
        fedilink
        arrow-up
        1
        arrow-down
        2
        ·
        1 year ago

        My point is, then use Lua outside of Vim. What does this have anything to do with the language used in Vim? You can use Vimscript in Vim, and still use Lua outside of Vim. So what’s the problem? It’s not like Lua gets available to you outside of Vim, just because you switch to Neovim. What do I miss here?

        • tetris11@lemmy.ml
          link
          fedilink
          arrow-up
          4
          ·
          1 year ago

          (it was mostly a joke, but) the skills you acquire tinkering your Vim to your needs using vimscropt can’t be used elsewhere, whereas Emacs has the (small) advantage that at least most of one’s elisp skills can be translated to common lisp quite easily.