Live data from Hacker News

Switching to Sublime Text from Vim in 2017

eduardobautista.com

51–60 of 71 posts

Re: Switching to Sublime Text from Vim in 2017

#51

Earlier quoted context omitted.

I think a lot of us can agree with the last bit, but that said VS Code is actually pretty darn nice.

Do you know how to remove 5 stupid menus on the left; explorer, search, git, debug, and extension. I don't agree with all these as default. Explorer (basically the nav tree): Just give me a toggle key and hide it by default please (I mean hide its icon nav too) Search: really? something + F is fine for short key like the others do. Git: I haven't even tried to use version control inside text editor. It is just illusi…

Put this in your settings file:

    "workbench.activityBar.visible": false

Re: Switching to Sublime Text from Vim in 2017

#52
post #2

Is VIM with plugins really that slow compared to Sublime Text? I'm curious what plugins OP was talking about.

Yes, just look for the most popular plugins. Or try using a popular "dotfiles" configuration, compare it with a raw Vim and it's really slow. With sublime you can have a lot of plugins and it doesn't affect the speed.

Before I switched to emacs I added any vim plugin that looked even possibly useful and usually didn't remove the ones I wasn't even using. I used nvim but didn't do anything fancy with plugins just used pathogen. A quick count shows 127 plugins. nvim loads instantly and exhibits no slowdown I can perceive.

I honestly have no idea where this nonsense comes from.

Re: Switching to Sublime Text from Vim in 2017

#53

I've recently switched from Sublime Text to Atom. I've used Sublime for a few years and was very unimpressed when I first installed Atom 2 years ago. For a long time it remained slow and clunky, but recently not only did they improve performance significantly but also made the whole user experience much easier and pleasant. I suggest taking a look at Atom before spending money on Sublime. The number of plugins and ex…

You may also try vs code, in my opinion it is better than atom, albeit not as flexible. Much faster, though.

Re: Switching to Sublime Text from Vim in 2017

#54
I went through a similar change, switching to Sublime a few years ago. However, I hate to say it as a die hard Linux enthusiast, Visual Studio Code is by far the best editor.

However, Vim always works. What do I mean by this? Chances are if you do any real development work, you are having to remote into another system. For sublime, VSCode, etc... you'll have to Mount the remote file system. Well that has failed me a few times, especially if the remote system does not support anything other than sshfs and you are on Windows machine. Terminal access means Vim. Vim just works 100% of the time.

So... I've come back full circle to Vim, because it just works and I don't have to change my workflow, because I'm in a different environment/borrowed machine.

Re: Switching to Sublime Text from Vim in 2017

#55

I hate these types of posts... "Why I'm no longer using vim and now using X" typically result from not digging into Vim enough. All the issues the OP is having have been resolved from either updates to vim, switching terminals, or just understanding vim basics. NOTE: Plugs can be slow and the OP is correct that some are hacky, but typically there's the Vanilla Vim solution to a problem that takes a little bit of read…

>If plugin speed is still a problem, learn why they're loading slowly, then dig into why rather than just saying "they're hacky or clunky".

I'd rather switch to an editor where I don't have to do that. After years of using Vim/Neovim, that's what I recently did. I'm planning to remove my Neovim config down to its bare essentials to speed it up and use it as a simple text editor, because that it does well; but even with a carefully tended for configuration, it's been a horrible experience as a programming environment.

Slow or buggy autocompletion (and I have tried it all with all types of configuration, deoplete, YCM, neocomplete, neowhatever, etc), problematic file management (NERDtree not playing well with the rest of Vim, netrw being buggy, VimFiler being slow), syntax highlighting being slow and often buggy compared to plugins from other editors... And then there's the whole having to glue together plugins that don't work nicely with each other, my god how many entire days have I wasted on that.

On the other hand, I have set-up Atom (for Elm) and VSCode (for everything else) with nearly no effort and no experience in very little time. And while their Vim-modes cannot compare, putting up with that is less stressful that putting up with a poor everything-else.

I have really high hopes for the Neovim project extracting all the text editing juice without the legacy, and to a lesser extent, the Xi editor (assuming Vim bindings are ever prioritised, otherwise it'll never be able to compete with Neovim); but right now, while Vim may be the best text editing experience it's nowhere near being in the same league of programming productivity of modern text editors.

Re: Switching to Sublime Text from Vim in 2017

#56
post #32

I think that the this "vim mode" plugin for Visual Studio Code has the best roadmap/checklist for supported vim features out there. https://github.com/VSCodeVim/Vim/blob/master/ROADMAP.md Every "vim mode" plugin should have something like that

In my experience both JetBrain's Vim plugin for their IDEs and the Visual Studio (not Code) plugin are better than the VSC plugin, but the latter is the best I've tried after those two.

Re: Switching to Sublime Text from Vim in 2017

#57
post #47

I hate these types of posts... "Why I'm no longer using vim and now using X" typically result from not digging into Vim enough. All the issues the OP is having have been resolved from either updates to vim, switching terminals, or just understanding vim basics. NOTE: Plugs can be slow and the OP is correct that some are hacky, but typically there's the Vanilla Vim solution to a problem that takes a little bit of read…

Last time I mentioned having switched away from Vim due to its plugins not giving the functionality I get elsewhere, the reaction was not good. As with the parent comment, somehow it was my fault, as I'd failed to update to the latest vim, changed terminals, or '[understand] vim basics'. I've been using various vi-alikes, including vim, since 1996, so, yes, I have used just about every vim plugin, used vi[m] on every…

The intent was not to insult the OP, rather express the problem with all the articles that are "Vim to Editor X/Y/Z" which all, typically, relate to Plugins & Performance. Most problems have solutions that just require more searching. Now I'm not saying you or the OP didn't take time to do this, but using plugins that are slow and bulky like CtrlP and syntastic have their alternatives.

I'm fine with the OP switching editors, I could careless which editor someone is using or switching to, but don't place the blame on plugin performance, plugin bloat, or building an IDE; Vim isn't an all-in-one solution and that's okay, we can push it to be an all-in-one solution.

My constructive criticism is that these problems are in every editor, don't pin it on vim plugins or the amount of plugins you're loading into vim. "releativenumber" is a valid reason to switch editors, but the rest of the reasons are applicable to all editors.

Edit: "switching terminals" -> "switching editors"

Re: Switching to Sublime Text from Vim in 2017

#58
You don't need to gratuitously bash the open source community because you don't like Javascript-based editors. It doesn't make any sense, you are just ranting. There are plenty of open source projects inspired by Sublime Text, written in many different languages and environments.

http://limetext.org/

http://edbee.net/

https://github.com/richrd/suplemon

https://plugins.geany.org/geanyextrasel.html

Since they are all open source, if you don't like something, just change it.

Re: Switching to Sublime Text from Vim in 2017

#59
post #43

> What I didn’t like about Vim was that a good number of plugins always felt like a hack. > Also, why not Emacs? I wanted to change my editor, not my operating system :P. He really made a mistake here, IMHO. Spacemacs is exactly the right solution here: can run on the console, can run in a GUI, meant to be extended (extending emacs isn't a hack: it's using emacs).

I briefly tried Emacs both alone and with Spacemacs. Spacemacs configuration is impenetrable, specially if you're not a LISP fan and Emacs simply needs a lot of glue to work well with Evil. Even then one has to know and use quite a few regular keybinds. At that point it just wasn't worth the effort to me over using a more modern and straightforward editor.

Re: Switching to Sublime Text from Vim in 2017

#60

To go to the reverse route, I'm a SublimeText and Vim user that's debating going back to pure vim. Much of the functionality that I used ST for I found Vim could do naturally, with no plugins. This presentation taught me alot ( https://www.youtube.com/watch?v=3TX3kV3TICU ), such as basic command completion. There is some stuff that Sublime can still do that I don't think Vim can (multi-cursor editing comes to mind, a…

Thank you you have just saved me weeks worth(or more) of time over my future lifetime.
Post reply on HN