News for hackers. Stuff that matters.
Re:Show HN: SpaceNeovim – Spacemacs for Neovim by Jeaye on Sunday September 18, 2016 @11:27PM (#12528653)
Having spent a month with Spacemacs, to give it a shot, and returning back to Vim, I've been craving some of the Spacemacs innovations. Unfortunately, we can't get elisp, which is a big selling point of Emacs for me, but Spacemacs' narrowing search menus, following SPC, and its community-configured layers make it often enjoyable to adopt a new configuration.

It comes at a cost though, the abstraction. Many say "the Spacemacs source is so readable; if I want to tweak something, I can just find what I want and go from there." In practice, I have never found this the case (likely since I've used Emacs for only 2 months) and I don't imagine I'd find it the case with SpaceVim/SpaceNeoVim either, even after having used Vim for half a decade. As a result, I consider these projects to be a more robust vim-sensible, which is a reasonable starting point, or common point, for new users, users who want to share a single configuration, or users who don't desire absolute control and just want some features to work (i.e. everyone but power-users). Fortunately, that suits a lot of people. More power to them and good luck to SpaceNeovim.

Re:Show HN: SpaceNeovim – Spacemacs for Neovim by flukus on Sunday September 18, 2016 @11:35PM (#12528677)
I really don't think elisp is particularly better than vimL. Emacs just exposes a lot more extension points than vim does.
Re:Show HN: SpaceNeovim – Spacemacs for Neovim by sooheon on Monday September 19, 2016 @03:48AM (#12529671)
That's really putting it mildly. Being able to evaluate any valid elisp form anywhere, directly or from a buffer, and affect the running state of the application, is pretty damn powerful. There is a point where the quantitative difference ("more" extension points) becomes so overwhelmingly large as to become a qualitative leap.
Re:Show HN: SpaceNeovim – Spacemacs for Neovim by flukus on Monday September 19, 2016 @04:20AM (#12529786)
> That's really putting it mildly. Being able to evaluate any valid elisp form anywhere, directly or from a buffer, and affect the running state of the application, is pretty damn powerful.

That's possible in vim too. You can manipulate variables (end redefine functions if you're sadistic) in ex commands. Similarly, every time I save a vimL file it parses and updates running scripts.