[ika]

Same here! I've been using both Vim (4 year) and Tmux (2 year) and I noticed I was actually spending more time configuring my text editor rather than just writing code. So I switched first to Atom and then to VSCode and I'm supper happy with the result.

[fredsir]

What are you guys doing with your configurations?

I've been using vim since 2009 and tmux for the last 5 years. Initially, I had to figure out how things worked, and that took some time, but I never spent any time configuring it now except if I find a new plugin and figure out a new feature I'd like to add.

[ika]

Nothing works out of the box, especially if you are trying to make two plugins work nicely with each other.

If you want IDE like features i.e Autocomplete than you have to spend days to make it work and even after that it doesn't work like other "GUI" editors.

+ Terminal interface is very limiting to have nice plugins...

I'm really glad I've switched to VSCode..

[fredsir]

> Nothing works out of the box, especially if you are trying to make two plugins work nicely with each other.

Indeed, but it doesn't really matter since the default experience in VSCode or IntelliJ or Xcode or any other IDE or editor doesn't work for me out of the box either. I have to change things anyways, and I can't change VSCode or IntelliJ or Xcode to fit my liking, but I've been able to change tmux+vim to it, although it could be even better.

> If you want IDE like features i.e Autocomplete than you have to spend days to make it work and even after that it doesn't work like other "GUI" editors.

For stuff like Go, Rust, Elixir, Python and so on, it works fine with when just installing the default "brand" plugin. Taking python as an example: even though "intellisense" in vim is worse than in pycharm, the rest of pycharm is so much worse than tmux+vim. "Intellisense" not being 100% in tmux+vim is not a dealbreaker for me at all. I can get by without "intellisense". But pycharm is so much worse for everything else than "intellisense", from basic editing to opening files to running shell commands and everything else I use all the time, which is a deal-breaker for me. For something like iOS+Mac development where I feel like I can't work without proper "intellisense", I do use Xcode.

> + Terminal interface is very limiting to have nice plugins...

Indeed, but still, even though tmux+vim sucks on some points because it's text-based, it doesn't suck enough to not be usable, and all these other editors and IDEs like IntelliJ, xcode, netbeans, sublimetext, vscode, atom and so on complete sucks for all the important things I need, which is a deal-breaker.

[maccard]

> Indeed, but it doesn't really matter since the default experience in VSCode or IntelliJ or Xcode or any other IDE or editor doesn't work for me out of the box either. I have to change things anyways, and I can't change VSCode or IntelliJ or Xcode to fit my liking, but I've been able to change tmux+vim to it, although it could be even better.

I disagree. The default settings of Visual studio work perfectly fine for me. As an added advantage, I can use other developers in my companies workstations to show them something quickly if I need

> For stuff like Go, Rust, Elixir, Python and so on, it works fine with when just installing the default "brand" plugin.

and so on? I'm a C++ developer. Setting up C++ autocomplete is anything but straightforward in vim and emacs

[fredsir]

> I disagree. The default settings of Visual studio work perfectly fine for me.

That's lucky for you, but unfortunately, it's not the case for me at all.

> As an added advantage, I can use other developers in my companies workstations to show them something quickly if I need

I might be using other peoples computers 10 hours a year, but I'm using my own maybe as much as 2200 hours a year. It doesn't seem logical to take the first scenario into account when deciding whether to customise ones setup or not, but it's indeed a nice bonus if ones optimal setup is the default one that every other developer is using too.

> and so on? I'm a C++ developer. Setting up C++ autocomplete is anything but straightforward in vim and emacs

I don't use C++ anymore, but 7 years back when I did, it worked good enough for my use case, and the problem with other IDEs and editors were the same back then as it is now, where they were actually hindering my work, which a less than perfect "intellisense" doesn't at all. YMMV.

[radix07]

Have you actually tried to get YouCompleteMe[1] to work for C/C++ autocomplete? It's a huge PIA. Autocomplete just works in VSCode and many other IDEs once you point them at the right directory.

https://github.com/Valloric/YouCompleteMe

[hellofunk]

I use Emacs for C++ and I've tried a wide variety of auto complete packages, never really getting them to work properly. And the result is that Ive learned that I can be just as productive without auto complete as I was with it. In fact, I might even be more insightful into what I'm working on, because instead of relying on a pop-up menu for an API, I actually have to look at API documentation and properly learn it that way , which usually gives me much more knowledge about what I'm trying to do

[wruza]

>Nothing works out of the box

Usually because the box doesn't have coreutils, make and exctags installed. Bloated plugins are snakeoil, they push vim to the dark^WIDE side, where the battle is too Pyrrhic to win.

[Touche]

Same exact experience here. Like, I could never get ES6 highlighting to work in Vim. Just flat out didn't work, so all non-ES5 code I write looks terrible. Could be a conflict with my theme or something else. I don't know, or care to do the work to figure it out.

I used Vim for a good 5 years. I still miss many things about it, but a shitty default UX is not one of them.

[fredsir]

I feel ya. tmux+vim looks terrible compared to for example VSCode. Problem is that VSCode just works much worse (for me at least) for editing code, navigation, running commands and so on, and I'd rather have an ugly editor that works great, than the opposite.

[syncopatience]

For anyone else who happens by and has the same issue, vim had (has?) substandard syntax highlighting for javascript. Pulling in pangloss's vim-javascript (https://github.com/pangloss/vim-javascript) fixed that up for me. If you write JSX, you can pull in https://github.com/mxw/vim-jsx to get great highlighting for that too.

[Touche]

I of course use vim-javascript. This didn't fix the issue for me. An issue with the color scheme I use I suppose.

[ika]

Yeah exactly... Main objective is just to write code, nothing more. No editor is perfect for me atm, VSCode eats my battery and it lacks some features but at least I'm only focused on writing code and having features that actually work...

[gjjrfcbugxbhf]

Or just install youcompleteme and get on with your work...

[stickperson]

I tried switching to VSCode earlier this week and am really having a hard time with it. I'm coming from iterm/vim/tmux. The most painful part has been the lack of a hot key to bring up VSCode. Besides that, I've found that switching between open files in vim (which I use <leader> and buffer number for) is much easier than VSCode (ctrl + number).

edit: Just opened VSCode again and noticed one other major thing that has been driving me crazy. In vim I often have files open in different panes and then make one pane full size while editing. Can't do that with splits in VSCode as far as I know.