3 ms·
As someone who tried to use Spacevim for a year+ I will say that a) it makes it more stable in a way, instead of your own hyper-custom config that could still b
by dmix 4y ago
As someone who tried to use Spacevim for a year+ I will say that a) it makes it more stable in a way, instead of your own hyper-custom config that could still break on updating vim/plugins you have a hundred plus other people having the same issues to debug it + a big community finding best of class Vim plugins doing the work of iterating it for you, but b) it's a bit rigid and even with the ability to tweak them you're better off either fully committing or not doing it at all because you'll be caught in between their complex config and your own breaking changes which is the worse of both worlds (as a starting config it's still very useful though).
This is ideal for people who can't be bothered to invest the time in a very personalized set up (like Linux desktop VS MacOS) but still want something more powerful and widely accessible than VSCode for most languages (the big exception being VSCode for Typescript/JS, as a Vim obsessed dev I've finally conceded to Code, since that's my day job).
- 3np 4y ago> the big exception being VSCode for Typescript/JS Why? As a neovim user with a lot of ts/js at $job, curious what if I'm missing especially useful (outside of the proprietary live-remote-session stuff)
- dmix 4y agoAlmost entirely because I develop Vue 3 w/ Vite on top of Rails 7 (plus a very opinionated Eslint + Prettier set up) so cutting edge plugin support = key, combined with a team that uses a mix of Vim and other stuff. VSCode's community will always completely dominate Vim for Typescript support and it's far easier to establish VSCode as the standard editor than a mix of custom Vim configs. Even the base Vue VSCode plugin + native TS engine doesn't support my needs for modern Vue 3 <script setup /> syntax without a ton of false positive redline errors. When I switched to using Volar my life became way easier (Neovims LSP plugins are usually a year behind the VSCode native ones let alone plugins): https://marketplace.visualstudio.com/items?itemName=Vue.vscode-typescript-vue-plugin https://marketplace.visualstudio.com/items?itemName=Vue.vsco... Otherwise our Ruby backend devs can use what they want. So can frontend but they'll be constantly fighting the current.
- INTPenis 4y agoYou're assuming I have a hyper-customized vim setup. Which I absolutely don't, I thought it was implied from my question that I am the opposite. I try to keep my setup as vanilla as possible because the main reason I enjoy vim is its reliability. And of course when I say reliability, I don't just mean from crashing. I mean from unnecessary work maintaining plugins and their infrastructure.
- dmix 4y agoIn that case it would 100% make it less stable. I respect the vanilla Vim folks but I could never do that. Just curious, do you also keep bash/zsh vanilla as possible? I hate sshing into servers without my rc, which is a downside. But I also don't do much sysadmin stuff so it's not a very common issue.
- INTPenis 4y agoI use bash, and yes it's pretty vanilla. I have a custom PS1 line with some added info but no colors, no multiple lines like a lot of people do. I've been using Linux (or Unix) for 25 years and it works well for me. I can work in large projects with many files and directories. I never even heard of people automatically transferring their RC files to remote servers. That sounds quite convenient to be fair.
- dmix 4y agoThat's cool. I'll always respect the diehards who value their longer term priorities over short term benefit.