Live data from Hacker News

Why I Still Use Vim

medium.com

171–180 of 209 posts

Re: Why I Still Use Vim

#171

I 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.

> I really wish developers stop using the JS editors and switch to platform specific editors

Why? How does what I use affect you?

Re: Why I Still Use Vim

#172
> Using Atom or Code I experience frequent freezes for several minutes when just typing a single character.

Sounds like a Linux problem. VS Code works great for me on Windows and the Apple Macintosh OS.

Re: Why I Still Use Vim

#173
post #158

Earlier quoted context omitted.

VS Code fairs quite similar to Atom in many tests in the linked article. But it does that by restricting what plugins can and can't do, and by integrating a large number of the functionality itself. I prefer to have the choice of multiple plugins each with their own tradeoffs, so I sacrafice some speed for it, but that choice can more than make up for it in many cases. And as for you claiming that web developers shou…

I hear a lot of talk about vs code. Tried it the other day was not impressed. For a full ide webstorm/phpstorm seems nicer but slower to load. Sublime text editor much faster. Vim much more portable. I even found dreamweaver 5 to have more features, (editing single files over sftp, accurate visual preview). Why is everyone moving to vscode? Is it a visual studio familiar feelings type thing or does it offer things I'…

It's all about the "little things". It's basically Sublime, except some core features like git integration (brought by gitguttter plugin in sublime), debugger gui, integrated terminals are baked in and "just work the way you'd expect" with the default settings.

Then there's the fact that the settings are either self-documenting or well documented online, so much easier to customize without spending time learning how to do it: just start editing the settings (btw, Sublime "stole" the 2-pane default/user settings ui idea from vsc) and figure out what does what as you go.

And then there's the fact that plugins seem to "just work" and "out of the box". With Sublime plugins I often had the "ok, I installed it, AND the other 3 things it needs to do it's job too, now how do I freaking use this poc?!" often followed by the keybindings being "wtf, this conflicts with everything else, no I have to think what my custom ones to be" etc. The whole "don't make me think", "don't waste my time" and "just works out of the box as expected" philosophy, adopted by most plugins too, and coupled with being just fast enough.

But yeah, with default settings VSC is annoying and looks bloated, but if you hide most of its UI and setup vim mode keybindings it feels like a superpowered vim :) Microsoft tends to be very good at "the little things" and at "discoverable UIs"... I still like Windows' UI most despite only occasionally using it nowadays for example: beyond the top layer of "monkey shit" (that you may need to hide/disable/reconfigure etc.) is a nicely configurable UI that caters well to power users.

Re: Why I Still Use Vim

#174
post #63

Earlier quoted context omitted.

Then try out the JetBrains IDEs, and report back. All the features, none of the slowdown. I can't believe a Java IDE is actually faster than the new default editors.

The JetBrains IDEs are far slower then VSCode. Granted they do more, but they're still slow. And this is on a top-of-the-line MBP.

I’ve ran the JetBrains IDEs on my thinkpad and desktop, and they’re consistently faster than VSCode when you compare them 1:1 (as in, you have a language plugin for that language + refactoring + co in VSCode).

Re: Why I Still Use Vim

#175

I recall the Turbo Pascal text-mode IDE that left enough space to actually run the programs you were developing. The machines had 640KB RAM, and I think the IDE was using perhaps as much as 100KB. I recall using fully-featured GUI IDEs like VB, VC++ etc on machines with whopping 64MB RAM, and having enough space left to actually run the programs you were developing. I have a laptop now with 16GB RAM. The other day I…

This is a strange story. Why did you download and install Atom and decide to test it for the first time on a large log file? Did you think that was what Atom would be good at?

Re: Why I Still Use Vim

#176
post #147

Earlier quoted context omitted.

How much RAM does the average developer have? I’ve got 16GB in both my 7 year old iMac and 4 year old MacBook Pro. I’ll probably get a new computer next year with 32GB of RAM. I don’t think an editor using 1G-2G matters to me. I don’t currently use Atom but if they innovate faster and eventually build a better editor, many devs will choose it.

The average is 8g still running windows 7.

Wow, it’s time to reread this:

https://blog.codinghorror.com/hardware-is-cheap-programmers-...

Re: Why I Still Use Vim

#177
post #111
post #84

Earlier quoted context omitted.

I wanted to agree with you and write a snide remark about Atom, but then I checked RAM usage of an empty Sublime Text 3 instance on 64 bit Linux, and it was at about 136 MB, so there's that.

Sure - there will always be an overhead for window compositing, etc. But the point of the article is the bloat as you open larger files, which gets much larger when you use a DOM to do syntax highlighting. I have (and unfortunately still have to from time to time) open massive log files - in sublime / vi / nano they open fine (even with syntax highlighting), but even on my workstation Atom and Code fall over.

Maybe the virtual DOM should be an actual virtual DOM instead of an additional DOM that doubles the materialized DOM (like desktop application's virtualized list and tree views since 20 - 30 decades).

Re: Why I Still Use Vim

#178
post #147

Earlier quoted context omitted.

The average is 8g still running windows 7.

Wow, it’s time to reread this: https://blog.codinghorror.com/hardware-is-cheap-programmers-...

The whole point is that many programmers, even in Western Europe, are not that expensive. When one makes less than $20k/year, those "mere" $4k suddenly pay for a full trimester of work, rather than less than a month.

Re: Why I Still Use Vim

#179

Being in 2 slack teams use up as much memory as the entire visual studio 2017 does on my machine. It is electron that is the root cause here and it is the same for all electron based apps.

Has anyone published a memory-map - a breakdown of what exactly is in the process' memory space - of these cases where Electron-based applications use orders-of-magnitude more memory than the native programs we used before? Previously I've remarked that high memory usage in web-browsers in itself is not a cause for alarm, and is mostly a good thing because it means the browser is aggressively caching assets so future…

Take Qt Creator for example. I'm now working with 20 medium-sized projects, consuming 305mb of RAM. Without any lag

Re: Why I Still Use Vim

#180

Most people in CA prefer to drive a car rather than ride a bike. Bikes use far fewer resources to accomplish the same thing as a car (go from point A to B), but most people like to have the option of turning on the AC, playing music, and all the other add-ons that a car can bring to the experience. I personally choose to bike, but if I started making charts about the relative energy consumption of the two, I'd reach…

This is an interesting analogy.

> Bikes use far fewer resources to accomplish the same thing

Bikes use a lot more time, which is a pretty important resource to most people. When I drive, that's usually why. So, are the additional features that Atom provides "driving saves significant time" variety or only "driving allows you to listen to the radio" variety? If the former, it might be worth the occasional freeze or slow down.

> If I used those charts to convince people to start biking, I doubt I'd be very successful.

I think if people actually didn't know that cars used more resources, the charts could have an impact on behavior. The fact that it's obvious (especially financially) means people already carpool or even (in cities) don't own a car at all. I don't think it's as obvious to some people that not every editor uses this much RAM, and you don't need another laptop upgrade, you can just switch to another editor.

> I couldn't care less... because it has practically zero impact on the environment or anyone other than yourself

I think you're right, but I'm not totally sure. If enough users refuse to use unreasonably resource-intensive software, then more effort will be spent on keeping most software efficient. We still seem to have plenty of options, but I'd rather try to convince others to use efficient software than eventually have to continually upgrade my hardware to keep up.

Post reply on HN