Why I Still Use Vim
31–40 of 209 posts
Re: Why I Still Use Vim
#32Earlier quoted context omitted.
Except that sublime does all of that, supports plugins written in python, and doesn't screen tear, and leaves me some RAM for other things
But Sublime doesn't do all of that. It does some things better, and others worse (and still others not at all). I couldn't write a plugin for Sublime to embed a web browser. I couldn't write a plugin for Sublime to display images inline by fetching their URL if found in the source. Those kinds of features might not be important to you, and that's fine, but they are indispensable for me.
Yes - that is true. and, with atom basically being a web browser, it is trivial for them to do it.
>I couldn't write a plugin for Sublime to display images inline by fetching their URL if found in the source
I actually think that is now possible in ST3. With the new "Phantom" plugin API it can certainly inject a subset of html (including tags) into the view.
Re: Why I Still Use Vim
#33Earlier quoted context omitted.
Except that sublime does all of that, supports plugins written in python, and doesn't screen tear, and leaves me some RAM for other things
But Sublime doesn't do all of that. It does some things better, and others worse (and still others not at all). I couldn't write a plugin for Sublime to embed a web browser. I couldn't write a plugin for Sublime to display images inline by fetching their URL if found in the source. Those kinds of features might not be important to you, and that's fine, but they are indispensable for me.
https://www.sublimetext.com/docs/3/minihtml.html
It is a bit different from when you are using a browser trying to look like a text editor, but still.
Re: Why I Still Use Vim
#34> I’ve primarily stuck with [vim] because it’s an extensible editor that doesn’t hog all the resources and kill my machines. Exactly, BUT ... Vim has a non-mainstream shortcut interface, which I've always thought is an unfortunate caveat. So over the years I've actually managed to massage Vim into behaving like a 'normal' editor. It fits into a plugin if you're interested: https://github.com/tombh/novim-mode
But then what's... the point? That vim has a rich and expressive language for text navigation and manipulation is the only thing that sets it apart from more modern competitors.
1. Modal editing. 2. One of the most ubiquitous, lightweight, stable and extensible editors in existence.
I just want there to be at least a semblance of a possibility to separate these 2 things.
Re: Why I Still Use Vim
#35[pushes up glasses]
There aren't ex commands ":ZZ" / ":ZQ", but "ZZ" and "ZQ" are normal mode commands.
Re: Why I Still Use Vim
#36It is electron that is the root cause here and it is the same for all electron based apps.
Re: Why I Still Use Vim
#37I really wish developers stop using the JS editors and switch to platform specific editors. It's 2017 and all platforms have great native text editors, like Notepad++, GEdit, and if you need cross-platform, Sublime text. I don't see the point I using these electron based editors which waste tons of CPU cycles, and provide nothing of value.
It's not wasting CPU cycles, and frankly even if it is, it's better than wasting my cycles having to switch between several terminal windows, apps, and file system browsers all because you don't think I shouldn't use an electron app.