Live data from Hacker News

Why I Still Use Vim

medium.com

61–70 of 209 posts

Re: Why I Still Use Vim

#61
post #55

Earlier quoted context omitted.

>with atom basically being a web browser, it is trivial for them to do it. Which was the point of them making it in a web browser. Leverage that as a platform to make extensions/plugins easier to write and maintain and allow them to do more. Atom is a more capable "IDE" than any other IDE i've ever used, and it's easier to create and manage plugins for. Yeah, there are still some rough edges and things that I hate ab…

> Atom is a more capable "IDE" than any other IDE i've ever used That says more about you than it does about atom. You should check out the IDEA line of IDEs sometimes.

I own a license and use IntelliJ's tools a lot still. Whenever I jump into Java code they are the gold standard! But when I'm working on web code, Atom runs circles around WebStorm.

Re: Why I Still Use Vim

#62
post #4

How much of that is fixed cost? i.e. how much of that 1Gb is still consumed if you have no file (or a single empty file) open and how much is consumed when you open a second 6MB file?

It took 256 Meg to open a 60 byte file. So we can probably assume that is the floor.

Was it the first file open? Or the first of it's kind? I doubt atom will use 2.5 gb to open ten 60 byte files.

Re: Why I Still Use Vim

#63

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.

Frankly, VS Code is WAY better in terms of plugin and configuration than any of the editors you mention.. from git integration, search, integrated terminal, integrated debugging with ui driven break points, etc, not even counting plugins. None of the editors you mention support those features. It's not wasting CPU cycles, and frankly even if it is, it's better than wasting my cycles having to switch between several t…

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.

Re: Why I Still Use Vim

#64
Blah blah this is ridiculous! Electron is horrible... blah blah... who cares? My macbook runs this fine and Atom is nice, blah blah, I switched to VS Code and its kinda nice, blah blah I tried this and went back to sublime... blah blah :q

Re: Why I Still Use Vim

#65
post #6

These kinds of comparisons always seemed a bit silly to me. It's like complaining that opening a 6MB file in windows took over 3GB on my system! (ignoring that most of that is the OS getting ready to do other things, and enabling the OS to do things other than opening and reading a 6MB file). Yes, Atom isn't the most resource friendly editor out there, and nobody is claiming it is. But it is one of the more capable e…

Reusing your own logic, Atom sucks because it is using a hammer (Electron) to turn some screws... Electron is the problem; it is completely ill-fitted for implementing an IDE

Re: Why I Still Use Vim

#66
post #53

Earlier quoted context omitted.

>with atom basically being a web browser, it is trivial for them to do it. Which was the point of them making it in a web browser. Leverage that as a platform to make extensions/plugins easier to write and maintain and allow them to do more. Atom is a more capable "IDE" than any other IDE i've ever used, and it's easier to create and manage plugins for. Yeah, there are still some rough edges and things that I hate ab…

Now, I haven't worked on web in a while, but what advantages does having an in IDE browser of a random provenance (it trails Chromium by 2-3 weeks) vs using a known version in a separate window beside it? edit: spelling

The same benefits that having multiple tabs of code windows is better than multiple separate windows.

When i'm debugging/developing/whatevering code that is going to run the same in all supported browsers, doing it in the editor directly allows me to switch tabs back and forth quicker and easier than having them as separate windows.

When i'm working on my laptop without any additional screens, being able to keep the view of the page on the same screen at the same time as the code is hugely beneficial.

When i'm at home I still tend to use a separate instance of the browser to "preview", but I still drop into the embedded one because the keybinding is so fast and easy to take a quick look then close the tab.

Plus being able to open bookmarks to random documentation websites and see the docs in the most up to date format in their "correct" formatting right in the editor is a huge bonus too.

Re: Why I Still Use Vim

#69

Earlier quoted context omitted.

This is ridiculous. I just should not complain that some program is useless and terribly resource hungry? What will be next? "Stop complaining that the browser uses 10GB of ram to show a page, as it is bigger than standard page"? This is just ridiculous. For showing the html I just use multiple browsers. My page must look good in multiple browsers, not in my editor. For the whole environment I just consoles with full…

You don't need to like Atom, but to claim it's a "bad editor" for everyone is silly. You can use multiple browsers to preview, I prefer to have it in the editor which makes it easier to switch between (same argument for code tabs vs windows). I still test and work in multiple browsers to ensure compatibility, but being able to get the rough parts laid out in the editor itself and fix/develop on things that are the sa…

> I don't need a car that goes 200MPH but that doesn't mean every F1 car is entirely useless, just that it's designed for a different purpose.

Those cars use huge resources for extreme performance. I don't think Atom provides extreme performance even after using extreme resources.

Re: Why I Still Use Vim

#70
post #50

Earlier quoted context omitted.

Which is fantastic for some use cases, but not for the use case where I want a fully featured browser window in my editor to preview my page i'm currently working on as I'm working on it.

Why not have one's actual web-browser as an adjacent window, with livereload? I think it's an anti-pattern for the primary application in use to be reflexively maximised and lay claim to the whole screen, meaning everything must be inside it.

If i'm working on a laptop with only one screen, an adjacent window starts to crowd the UI pretty heavily. Having it in a tab is easier for me.

You can call it an anti-pattern, but for me the anti-pattern is alt+tabbing back and forth to see if my changes look good, or cramping the browser to 1/2 the screen and the whole editor (with sidebar, file tree, and other crap) cramped in the other half, or needing to navigate to localhost:3000 every time I want to look at something VS having a keybinding to open to the exact page i'm working on.

Post reply on HN