Live data from Hacker News

Why I Still Use Vim

medium.com

11–20 of 112 posts

Re: Why I Still Use Vim

#11
As far as I can see from this article, Sublime text is faster than vim.

That's astonishing considering that Sublime uses GUI and vim is a console editor.

I also like vim, but Sublime + vintage ( vim-mode ) works good and you have the benefits of both worlds.

Re: Why I Still Use Vim

#12
post #8
post #2

Last posted 133 days ago: https://news.ycombinator.com/item?id=15079857 The title should be same as the blog post title: "Why I still use Vim".

You can also use properly designed IDE's written in native code. I use Vim too by the way.

I use an IDE written in non-native code (IntelliJ) and I can have dozens of files open, while the IDE does error checking in the background across thousands of files, and it uses around 2GB of memory in that situation. 800MB for one file is insane.

This isn't just a contest between native and non-native code. It's a contest between efficient non-native code and crap non-native code.

Re: Why I Still Use Vim

#13
post #6

Earlier quoted context omitted.

They have been doing that for some time. Not sure how effective this is.

Kind of shady, I don't think I will write on this platform anymore.

What's shady about asking people to pay for content? It seems like it's pretty much out in the open so you can take it or leave it, not secret or covert or shady in any way.

Re: Why I Still Use Vim

#14
This article implies the differences matter. Nope, sorry, the conveniences of VSCode are worth the "cost" for me. I have 32 gigs of RAM and the time I spend opening files doesn't register compared to the time I spend writing or reading code.

I do wonder whether the measurements take the base overhead of each editor into account. Do the numbers represent the use per file or the total for the file plus the entire app?

Re: Why I Still Use Vim

#16
I really wanted to like Atom, but it always felt unfinished and clunky with crashes/freezing/locking becoming more of a regular occurrence with the more plugins or extensions you use.

It's one saving grace is that I thought Sublime was a bit bulky/memory hungry, but Atom gave me a new found appreciation for Sublime which I'm now back in love with!

Re: Why I Still Use Vim

#17
post #8

Earlier quoted context omitted.

You can also use properly designed IDE's written in native code. I use Vim too by the way.

I use an IDE written in non-native code (IntelliJ) and I can have dozens of files open, while the IDE does error checking in the background across thousands of files, and it uses around 2GB of memory in that situation. 800MB for one file is insane. This isn't just a contest between native and non-native code. It's a contest between efficient non-native code and crap non-native code.

To be fair they picked an example that really highlights a weakness in atom (parsing and syntax highlighting XML files), and this article is a bit older (at least in terms of atom and electron releases).

Right now I have Atom open with four different projects. Each project has anywhere between four and twelve files open. The project using the most memory is only 258MB, but the others are all close to 100mb.

Re: Why I Still Use Vim

#18
I find that I actually use both vim and GUI editors.

If I'm writing a lot of fresh code or exploring a new codebase, I like to use GUI based editors.

Anything quick or repetitive, I tend to open up vim because its speedy to open and edit.

Re: Why I Still Use Vim

#19
(this was in reply to a comment that has been deleted)

Well, Electron has finally delivered on the original GUI promise of Java over a decade ago: every single application I use on a daily basis is now cross platform.

That matters to me because it means it doesn't matter what OS I'm using - I can recreate my setup on Windows or macOS if I can't use Linux. I don't have to worry about platform differences beyond the shell and filesystem.

The security concerns people have with Electron are great but I'd wish they applied the same skepticism to all applications written in C++ or C. Unsandboxed applications are inherently unsafe. They don't just suddenly become unsafe because you write them in JS.

Re: Why I Still Use Vim

#20
post #6

Earlier quoted context omitted.

Kind of shady, I don't think I will write on this platform anymore.

What's shady about asking people to pay for content? It seems like it's pretty much out in the open so you can take it or leave it, not secret or covert or shady in any way.

It's shady if they're not giving out royalties to the writers. Not sure if they do
Post reply on HN