Live data from Hacker News

Show HN: SpaceVim Release v1.5.0

spacevim.org

21–25 of 25 posts

Re: Show HN: SpaceVim Release v1.5.0

#21

I went through the install process on windows. First it said I need to install gvim first. So I did that. then set the path to gvim.exe Then I was able to install it, and it said just start gvim and plugins will install automatically. So I start gvim and nothing happens. Looks like normal gvim. I feel like these sorts of experiences are always what happen when using kinda linuxy tools. Compare to installing vscode wh…

we recommend to use neovim instead.

Re: Show HN: SpaceVim Release v1.5.0

#22
post #3

Interesting. So, clearly modeled very closely after Spacemacs. Why would someone use this over Spacemacs in vi mode? (I’m sure there are reasons, just curious what they are)

Spacemacs feels really really brittle. Probably not for people familiar with Emacs, but for vim users it (usually) does. I am imagining that this package might feel smoother for a vim user to maintain since it's vim-native

Re: Show HN: SpaceVim Release v1.5.0

#23

I went through the install process on windows. First it said I need to install gvim first. So I did that. then set the path to gvim.exe Then I was able to install it, and it said just start gvim and plugins will install automatically. So I start gvim and nothing happens. Looks like normal gvim. I feel like these sorts of experiences are always what happen when using kinda linuxy tools. Compare to installing vscode wh…

> I feel like these sorts of experiences are always what happen when using kinda linuxy tools. Compare to installing vscode where it just works.

Spacevim is not an editor, that would be vim/gvim, which works fine as you said yourself. Spacevim is a collection of configurations, basically a plugin, and those are working on VS Code as good or bad as on any other editor.

Re: Show HN: SpaceVim Release v1.5.0

#24
post #3

Interesting. So, clearly modeled very closely after Spacemacs. Why would someone use this over Spacemacs in vi mode? (I’m sure there are reasons, just curious what they are)

Emacs has problems of it's own which vim often does not have. Sometimes those are even quite serious. And evil is far from being perfect itself and still somewhat alien in emacs-space. So staying with vim and just enriching it is also a good solution when you don't wanna buy into a new platform.

Re: Show HN: SpaceVim Release v1.5.0

#25
post #3

Interesting. So, clearly modeled very closely after Spacemacs. Why would someone use this over Spacemacs in vi mode? (I’m sure there are reasons, just curious what they are)

While Evil mode is good, it is not true vim. That could be one particularly strong reason. There is also performance, emacs is slower than vim, unless you set up an emacs daemon at startup.

daemon only helps with startup, it does not solve the runtime-bootlenecks. Though, there are settings to minimize those, and other soltions in progrewss which might hit emacs-master in some years.
Post reply on HN