1. 27
  1.  

  2. 11

    The downside to this is that the reason emacs is awesome it because it’s essentially a lisp VM. In vim land you have vimscript. They don’t even compare

    1. 6

      And emacs can show images inline. This is e.g. used to preview LaTeX equations in org-mode, AUCTeX, etc.

      You can even use emacs + org-mode as a Jupyter-like notebook, with executable code blocks where matplotlib outputs are shown inline, etc. As a bonus, you have git manageable plaintext rather than a big JSON blob (as in Jupyter).

      1. 1

        Agreed. It is worth point out that they are using some neovim-specific plugins, which should help things since they can be written in python, lua, etc.

      2. 5

        For a Vim user of about 15 years I have mixed feelings about these things. In a sense this feels like Linux in the sende there are somewhat-compatible distributions and you can’t talk about using Linux or Vim without qualifying a lot.

        “I use SpaceVim but replaced Syntastic with ALE” and blah.

        Guess there’s some point in lowering the bar for entry, but these big editors are technical programs. It would be better if people put in the effort to learn them as they are and expand where required.

        1. 1

          It would be better if people put in the effort to learn them as they are and expand where required.

          Especially with vi/vim/neovim! With spacemacs a novice user can hit the ground running, meanwhile, a spacevim user is still going to hit the fabled first session. Lowering the bar for vi is just delaying the inevitable learning cliff climb!

          1. 4

            Lowering the bar for vi is just delaying the inevitable learning cliff climb!

            To be fair, Emacs has the same problem. To be even more fair, Spacemacs users are going to hit the exact same fabled first session.

        2. 3

          This looks pretty interesting! I’ve been considering switching to Evil Mode, but maybe some of this material will convince me to stay for a bit longer :P

          I do wonder about the usefulness of these sorts of projects overall: I’d argue that most developers would prefer to build their dev environments from the ground up, rather than inheriting a whole slew of keycommands they haven’t defined themselves (also, I like to avoid language-specific plugins for languages I do not use :P)

          That being said, this looks very well thought out :)

          1. 2

            Lazy loading gets rid of most of the issues around language specific plugins, but I guess what will make or break this is how well integrated the plugins are and how heavy this all ends up being. I like spacemacs, but it’s a little clunky. I’ll try this out when I have the time.

            1. 1

              A lot of this went away for me when I started using emacs in daemon mode. Granted, it’s a pretty silly suggestion to run your text editor in a daemon. :)

            2. 2

              I don’t think of spacemacs as an evironment as muich as I do a separate app that runs on the emacs vm

              1. 5

                Did you ever play a “total conversion” mod for a game like Quake or Unreal or Half-Life? Usually the experience you get is mostly seamless and all new but then occasionally a little bit of the underlying game that it was based on pokes through and is visible - say a stray texture or something that was reused from the base game.

                That’s kind of how using Spacemacs feels relative to Emacs. :)

              2. 1

                I’ve been using vimrc for a while (because I lost my original setup) and I keep forgetting combos for things like opening NERDTree, etc… I think because I didn’t set them up myself, it didn’t sort of burn the keystrokes into memory. vimrc has too many things in it for me. This looks a bit more lean by comparison so I might actually try this out to put off setting up all my own again.

                Edited: meant vimrc not vimawesome

              3. 1

                What does “dark powered” mean here? I thought it meant “supports a dark theme” but I can’t really tell.

                1. 1

                  Some kind of Star Wars joke by the author?

                  1. 1

                    I think I found the answer on vi.stackexchange:

                    “Dark powered” is a phrase that you are going to find in Shougo’s vim plugins that have support/or are only for NeoVim.

                    “Dark powered” comes from the “Light Vim users”- those who only use default features and “Dark Vim users”- those who try to use it as IDE or at least use a lot of plugins and have a lot of lines added to their vimrc file (more about it here in Shougo’s presentation- slideshare.net/Shougo/lets-talk-about-neovim - slide 6)