# SpaceVim vs SpaceMacs

**URL:** <https://forum.devtalk.com/t/spacevim-vs-spacemacs/1323>\
**Category:** Code Editors\
**Tags:** vim, emacs, spacevim, spacemacs, code-editors\
**Created:** [14 August 2020 22:14 UTC](https://forum.devtalk.com/t/spacevim-vs-spacemacs/1323 "2020-08-14T22:14:12Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![hauleth](https://forum.devtalk.com/user_avatar/forum.devtalk.com/hauleth/32/599_2.png) [@hauleth](https://forum.devtalk.com/u/hauleth)\
**Post date:** [23 August 2020 18:38 UTC](https://forum.devtalk.com/t/spacevim-vs-spacemacs/1323/13 "2020-08-23T18:38:22Z")

</div>

If I would spot this circa 10 years ago, when I was starting to use Vim my mai editor, then I would probably be amazed. However nowadays I wholeheartedly disagree with basic idea of these projects - sharing editor configuration. Instead I prefer (and advocate) to write your own configuration, let’s be honest, it is not that hard. These projects are nice as long as:

- everything works
- your workflow is similar to authors

If any of these points is not true (or at some point became not true), then you will (pick one):

- drop the editor, as “it do not works like I want” (and probably later rant about it in the internet)
- create GitHub issue and wait till it is resolved by someone (probably never) and in the meantime use “workaround”
- learn configuration language yourself, which mean, that you didn’t need the “framework” in the first place

It is especially annoying when later I need to explain people that Vim has built-in completions (yes, many of them) and difference between completion and _auto_completion. Or any other similar stuff, like building project from within Vim, running tests, file browsing, project navigation, status line, tabs vs buffers, etc.

---

_[View the full topic](https://forum.devtalk.com/t/spacevim-vs-spacemacs/1323)._