r/coding • • Oct 04 '13

Just use Sublime Text (instead of vim)

http://delvarworld.github.io/blog/2013/03/16/just-use-sublime-text/
43 Upvotes

254 comments sorted by

18

u/semioticmadness Oct 04 '13

Another claim of "Old, Mature Thing is hard! I promise New, Immature Thing doesn't have those hard-to-understand features, and only has what you need!"

10 years later, it will be: "Don't use Sublime Text, just use the next thing. Sublime Text has too many hard-to-understand features"

19

u/JW_00000 Oct 04 '13

And what's the problem with changing editors every 10 years? If something better comes along why not switch to it?

11

u/semioticmadness Oct 04 '13

This is really just my opinion, and I was being snarky, but my point of view is that these things are hard because they cover a truckload of use-cases. So after you start to pack in all these crazy use cases, the whole thing gets over-full, and then you have to remember 10 mouse-clicks to configure the feature that you must have but you can't find more than 2 forum threads on Google on how to use it...

Notice that Vim's turn-off is because of how it does what it does, not what it doesn't do? Too many crazy keystrokes, but if you get them, you can do some crazy-awesome stuff.

This isn't just Vim. I see it in MS Word, C++, Sendmail... Sublime Text will get there if it remains popular for another 10 years, as feature-creep takes the shine off of it.

1

u/dhvl2712 Oct 05 '13

Old can also mean outdated.

→ More replies (1)

50

u/MediumRay Oct 04 '13

As ever, I say take the rants of bloggers with a pinch of salt. Some things I agree with, (vimscript is pretty whacky). And others I don't (vimscript is hard to learn, most vimmers don't know vimscript). I would like to see the justification for those statements.

"Vim is more efficient is dubious and untestable"

I guess that would be true for all editors, yes. You can't 'prove' efficiency.

Don’t you ever think you can beat a mouse. Only in very few edge cases will it even matter.

Suddenly an expert on efficiency, can definitely say a mouse is better.

In my opinion, you would be mad to say a mouse is anywhere near as efficient, barring very few exceptions. Also you want monospaced characters always, otherwise you can't select/move blockwise. Obviously someone didn't read those two books.

My advice has always been: if you want to be able to edit code at the speed of light, and are willing to put in some time to learn how to do so, vim is for you. Especially if you spend a lot of time on the command line and are editing many files at random that aren't necessarily all one project. If you are more interested in the stuff an IDE has to offer, you can probably forgo vim (not that it can't be used with/as an IDE). Overall I get the feeling the author doesn't use vim all that well.

9

u/[deleted] Oct 05 '13

I don't understand why anyone gives a fuck if its 10% faster to edit code in Vim over any other editor. The time I spend physically typing is probably 1% of the time I spend working. Coding isn't typing, its thinking. Spending time optimizing for typing is a waste.

6

u/MediumRay Oct 05 '13

You spend time thinking, and then once you have done that, what you realise you want to do you can do much faster. For a lot of tasks I do I never stop to think so for me it is worth it.

6

u/brettins Dec 05 '13

I'd say the big thing is how much thought and effort it takes to do whatever I think affects my continuity of thoughts, which is ABSURDLY important for my coding. Switching to mouse means I shift my weight, mode of thinking, whereas staying at the keyboard and getting someplace instantly is very helpful to me. Might not be the case for anyone else, but maybe this will help you understand why someone gives a fuck :)

1

u/HuckleberryPowerful7 Jul 01 '26

you wanna think more, type les

2

u/nairebis Oct 28 '13

Don’t you ever think you can beat a mouse. Only in very few edge cases will it even matter.

Yeah. That's when I knew this guy had no idea what he was talking about and is probably a slow typist. There is no way that lifting your fingers off the keys is more efficient.

And I didn't get the impression that he really understands the power of Vim for everyday editing, such as the repeat ('.') command.

1

u/MediumRay Oct 30 '13

Indeed. Although, if you are a slow typist, then using the mouse could be better (if you are really really slow).

4

u/pohatu Oct 04 '13

If I were on a terminal editing text over a 2b connection of whatever they had when they invented vi, I'd totally find it awesome that I could count lines and then tell the cursor to jump 20 lines by typing 3 letters rather than typing down 20 times.

but I can't seem to understand how counting lines and then entering a command is faster than just scrolling and clicking. Find is faster than scrolling, sure, but clicking 6 lines below is faster than counting to see its six line I want to go to. Maybe you get. A habit of line number subtracting or something.

12

u/MediumRay Oct 04 '13

I actually use relative line numbering, so I don't need to count the lines (the line my cursor is on is numbered 0, lines above and below go 1 2 3 etc.). But, that isn't really that fast, and I don't use it much, because you need to type 20 then down, then move right somehow to get where you want. Clicking might even be faster. No, what I do 97% of the time is search forward. So if I see that I want to edit a line way down saying println("This is a test");, I would search forward for 'This'. The cursor jumps there. I then hit 'ci"', which means 'change inside the "s (delete what is currently there and prepare to insert text). After that I can jump back to where my cursor was before in a keystroke, or whatever. So you can move faster, I would say. Moving lines around is the fastest though, instead I could have jumped to that line, hit the keys for 'copy line', then jumped back to where I was to paste it there. That would take way longer with a mouse (for me at least).

1

u/unknownmosquito Oct 05 '13

Not to mention you can just enable the mouse, even in console vim or Evil mode in emacs.

Task: I want to change the text inside the quotes of "This is a test" visible halfway down the screen.

Sublime: Click carefully before the T and drag to the end of test. Begin typing.

Vim/Evil Mode: Click quickly anywhere between the quotes. Type ci" and begin typing. Or jump there with f or /. Or use easymotion. Or use line numbers. You know, whatever's fastest. I guarantee you can do it faster in vim.

6

u/Tenobrus Oct 05 '13

Actually...

Sublime: Click quickly anywhere between the quotes. Press Shift+Ctrl+Space and begin typing.

1

u/rs-485 Oct 05 '13

What about brackets? You can do ci( in vim, how do you that in Sublime?

3

u/Tenobrus Oct 05 '13

Shift+Ctrl+Space is actually just "expand selection to context", so it will still work. Or Shift+Ctrl+D, which is specifically "expand to brackets".

→ More replies (8)

1

u/MediumRay Oct 05 '13

It becomes really obvious it's a better option than the mouse when you have to do it multiple times. I mean, changing what is inside the quotes in a = "this is so..." + "why " + keyword + "me";. Using the mouse requires careful selecting and retyping. Vim, just jump between "s changing the contents. If you want to change some of them to similar things it also requires only a keystroke.

→ More replies (1)

1

u/mirhagk Oct 06 '13

click line, shift+delete, click line, ctrl+v.

Highlight line, (from end of one you want, to end of one above, takes no time at all), then drag section to new line you want.

Alt+up arrow, Alt+down arrow.

I don't know about you, but I find any of this 3 MUCH easier (and faster) to use than any archaic set of commands. Unless you very imtimately know the code you're working on, you still need to look for where the line you want is.

Anyways, I prefer an editor that knows the language rather than an editor that makes guesses based on text. Go to definition, find all references, and having them actually work based on the code itself (where it actually finds all uses, and not just similarly named functions/variables) is WAY more useful than anything vim could possibly offer.

1

u/codygman Nov 25 '13

Vim does offer "Go to definition, find all references, and having them actually work based on the code itself (where it actually finds all uses, and not just similarly named functions/variables)" via rope.

why do you assume a GUI program has something which vim cannot have? They are both programs.

2

u/mirhagk Nov 25 '13

why do you assume a GUI program has something which vim cannot have?

The GUI program has one thing vim cannot have. That's a non-steep learning curve. Right click or click the menu options and you'll see everything that visual studio can do, as well as the keyboard shortcut for next time. Vim requires looking up documentation for doing anything.

4

u/nairebis Oct 28 '13

I guarantee I can type six j's in less time than you can reach for the mouse, find the click place, and get your hand back to the keyboard. I can probably type 20 j's faster (though, I'd probably just do 20j).

Generally speaking, at least for me, I don't do exact counts, I just do 20j and go up or down a couple of lines. Once you get used to Vim, the keyboard becomes an extension of your mind. You don't think about it anymore, you just edit. Leaving the keyboard to hit the mouse totally interrupts my flow of thinking.

I kind of suspect that if you did a survey, the people who prefer Vim are also the people who type the fastest and are able to edit without their eyes ever leaving the screen.

1

u/reasonably_plausible Nov 25 '13 edited Nov 25 '13

the people who prefer Vim are also the people who type the fastest

They'd also be the people who think that typing the fastest has anything to do with coding well.

1

u/nairebis Nov 25 '13

I wouldn't say that fast typing leads to great code, but I would note there is a correlation that great coders tend to also be fast typists, probably mostly because both require time and practice. In my experience, I would also say great coders have a general desire to have their thoughts be entered into the computer as quickly as possible, so they have more passion/incentive than "just a paycheck" people to push themselves to type faster.

But even beyond code quality, I would also venture that faster typing (and faster text manipulation in general through tools such as Vim) lead to more productivity. Some might put "productivity" in the metric of how well someone codes, which doesn't seem unreasonable to me.

1

u/reasonably_plausible Nov 25 '13

but I would note there is a correlation that great coders tend to also be fast typists,

source? At least for faster typing beyond simple touch typing, because I will agree that coders will learn to touch type, which is faster than the average person's typing.

I would also venture that faster typing (and faster text manipulation in general through tools such as Vim) lead to more productivity.

If you were spending the majority of your time typing, that would increase your productivity by a significant factor. But typing isn't anywhere near the top bottleneck for a coder's productivity.

1

u/nairebis Nov 25 '13 edited Nov 25 '13

source?

Just personal experience. I actually can't think of anyone I would tag as a "great coder" in my 30 years of experience who wasn't also a fast typist. Edit: To be fair, I'm sure there were a couple, but they weren't slow enough that I thought about it. And I've always been usually the fastest typist of the group, so it wasn't remarkable for someone to be a bit slower than I was.

But typing isn't anywhere near the top bottleneck for a coder's productivity.

If they're not typing most of the time, then I don't know what else they're doing. I mean sure, sometimes I need to go back and read the code to see what it's doing if I'm debugging, but otherwise I'm either typing in code or typing in debug code, or typing in commands to run the code, or something else that involves typing. But then, I'm also old school that my IDE is six Putty windows running Bash across two screens, and I rarely use debuggers (they are the slowest way to find bugs, but I won't try and prove that to you, if you're not already a believer. :) )

→ More replies (3)

2

u/brettins Dec 05 '13

I rarely use the jump 20 lines command, but I almost ALWAYS use "123G" which will take me to line 123 instantly. Super fast, super easy.

2

u/Guvante Oct 04 '13

I guess that would be true for all editors, yes. You can't 'prove' efficiency.

Actually you can, if you can remove tester knowledge from the equation. Ask Microsoft, they have a ridiculous amount of information on how to make the Office UI more efficient.

However if you want to measure an experienced user those metrics become impossible to obtain, as how do you define experienced?, how do you find the group you defined?, etc.

Suddenly an expert on efficiency, can definitely say a mouse is better.

I think he is more pointing out most people have a cognitive bias for shortcuts to move the cursor. He is also specifically talking exclusively about random movements, not controlled ones. (I need to go to the third word of the line 6 above me)

Also I thought his emphasis was on the later point, that it typically doesn't matter.

Also you want monospaced characters always, otherwise you can't select/move blockwise.

Obviously someone missed the entire context of his anti-monospaced comment in the UI's added by add-ins. He wasn't saying use a non-monospaced font for text editing (although you have to admit that the option to lose block edits is sometimes worth it).

if you want to be able to edit code at the speed of light

And other people would say an IDE improves your correctness and productivity so much that choosing VIM is a non-start. It is inherently a personal thing.

and are willing to put in some time to learn how to do so

You are sidestepping his entire article by saying this in this context. His point was VIM doesn't provide the efficiency improvements soon enough to justify the time it takes to learn it.

To put arbitrary numbers on it, if you are 50% slower for a month, 20% slower for the first year and 5% faster from then on, your break even point is almost 6 years from now. A 10% first year penalty leaves you at 4 years break even.

The other point he was trying to make is that VIM is heading down a dead end path that means it won't be making any significant improvements in the future.

6

u/MediumRay Oct 04 '13

I don't think you can define efficiency in any real sense. I mean, you could say vim IS the most efficient because you need the least amount of keystrokes to get something done. But then by that metric, having an editor that had some sort of huffman coding on the keystrokes to minimise the amount needed would be technically more efficient, just impossible to use.

You think he is talking about cognitive biases? That's a bit of a stretch, I'd say. And, I am not sure what random and controlled movements are, tbh. But, the mouse argument isn't good anyway, most of the article wasn't, - he just says the mouse is good at screen jumps, you can't beat it (no other rationale) (because vim doesn't have anything that is targeted for jumps, no sir).

He wasn't saying use a non-monospaced font for text editing

So, if you are not editing, you are either reading, or just creating linearly. Vim is a text editor. In those scenarios, you don't need vim any more, you can just read it in word right? I would never choose to forgo fixed character widths, since the only benefit to not having them is aesthetic and it doesn't bother me (although I can see that others might be).

And other people would say an IDE improves your correctness and productivity

I said edit code, quite specific on the 'edit' part here - there are many times an IDE will keep you on the right track better than vim (at what I would say is the cost of not being able to edit the code as quickly). To me, an advantage is that vim can edit any code, whereas you have different IDEs for different tasks. So, I am currently editing a makefile. Open file, change stuff relatively quickly. Save, open a perl script that the makefile calls in another tab, vim changes the syntax etc. when I go to the perl file. When I save, it checks the perl file for errors. Suspend vim with CTRL-z (bash command), run make. Back to vim, open now the text file the perl file created in another tab. Run commands on all tabs, and so on.

VIM doesn't provide the efficiency improvements soon enough to justify the time it takes to learn it

Well yeah, I got that. I can't disagree that if you want to start coding in the next week, vim is not for you. Also, his points aren't necessarily that it doesn't provide the improvements soon enough, more like there is no/little improvement (mouse argument etc). But, my advice part was for the most part unrelated to the article and just my view - decide what you want in an editor, then go for it. They all have different things to offer.

2

u/mirhagk Oct 06 '13

So, if you are not editing, you are either reading, or just creating linearly

I was under the impression most people wanted to be able to read what they were editing. You just memorize it all? Being able to make the important stuff stand out, and the rest fade into background is actually hugely beneficial and something that vim sucks at (it all looks equally important).

You can define efficiency in terms of how much time it takes a typical user to accomplish a task, look at average, best, worst, 10% best, standard deviations, improvement over time, or one of the other countless ways smart companies look at efficiency (companies like Microsoft who collect user data, and base decisions on that rather than blindly guessing, or basing it on their own usage).

I watch people who've used vim for years, and even they struggle to do things that take me very little time to do in my IDE (after having roughly the same amount of experience with it). Refactoring is probably one of the biggest ones. In my beautiful IDE I can refactor code completely safely, the editor knows what sections of code means, knows which function references which variables (not based on names, which fails when you have the same variable mentioned twice), and can work across several different files very naturally. I can view call heirarchies for various random methods and classes, and it'll just work.

Best part of an IDE, you don't have to know ANY shortcuts. Yes it'll make it faster, but pretty much anything you can do with shortcuts you can right click and select the option. It also shows you the shortcut, so the next time you'll be able to use it. IDEs you learn by doing, and get better naturally, vim you study in order to do anything.

1

u/MediumRay Oct 06 '13

You said that he didn't want the monospaced font for editing. He wants to only read his stuff right? You can't have non-monospaced, AND full editing functionality.

I don't feel vim sucks at making important stuff stand out. set syntax works for me. You can turn on italics and bold too if you want (in gvim), but I don't. I guess that's up to you.

you can define efficiency in terms of X Y Z A B C

This was kind of my point. You can't say 'this is a more efficient editor'. There's no metric. Not that this is particularly important.

IDE ...refactoring ...finding definitions

Yes, as I have pointed out, vim is not an IDE, although you can make it as such (refactoring and jumping to variable definitions etc.) if you really want.

I don't really think you get it. Your Shift-Del command example is kindof pointing out where it is faster to use a command than the mouse. And, I had never heard of that command. I guess for me to get the benefit of it, I would have to learn it. Learning the vim commands is relatively easy. All the keys stand for something. So when I want to change the text inside brackets, I do ci(. My mind thinks 'Change inside the (', and so on. Now, I find my hands do it as I think of it, which can be disconcerting.

Also, the good thing is you don't have to intimately know the code to still edit it fast. You know that below you have a printf that has your keyvalue string. do /print.*key to jump to it, wherever it is, yy to yank the text, '' to jump back to where you were before the search, p to paste it.

Trust me, depending on what editor you're using, I can think of 100 common situations where using keyboard commands is noticeably (or drastically) faster.

1

u/mirhagk Oct 06 '13

Yes, as I have pointed out, vim is not an IDE I know vim isn't an IDE, it's a simple text editor, it works great when you can't find good IDE support for a particular language, or you're forced into the terminal (server)

Trust me, depending on what editor you're using, I can think of 100 common situations where using keyboard commands is noticeably (or drastically) faster. It is definitely not faster when refactoring, and working with code you don't know very well, or that is very large. Even you're print example required you knowing that there is a printf below. If you can see the code on screen it may be marginally faster to jump there by using keyboard shortcuts than by the 0.5 seconds it'll take to jump there with the trackpad, but when your code isn't on screen (because you're not programming in K) and you don't know what to type to jump there, using a scroll button on a mouse is MUCH faster to navigate, I don't even think you can argue that.

Vim is meant to quickly edit a code, and maybe it is slightly faster assuming your comparing it to a "dumb" IDE that doesn't understand language semantics (instead of just syntax), but writing code is less than 10% of a programmers job. 90% of it is reading and reasoning about it. An IDE makes it so much better to read and explore code.

The commands in vim may be easy to remember when you study a textbook and have to type them out on a test, but an IDE will let you discover them automatically (right click, see options, as well as shortcuts for next time), so you don't have to think about learning your text editor.

1

u/MediumRay Oct 06 '13

Haha, I don't think you can outright say it's 'definitely' faster, but whatever. I can't say that I have ever refactored code that wasn't mostly my own, but I don't generally have a problem with medium-sized code. I can say 'jump to function definition', even if it's in another file, it opens that for me etc., or, copy a function a few times, then do regex substitute on the variables inside it (I wouldn't want to use an IDE that doesn't support regexes). I have heard, though, that you really do need an IDE for huge codebases (not something I have or probably will work with), so yeah.

I don't know if I agree with the 10-90% split. I am currently doing a lot of data processing which would be much more difficult without vim, or at least some perl scripts. I usually create a file full of 10,000 lines, and then start to remove all lines that contain or don't contain strings, and inspect/jump to next string etc. Doesn't require much thinking, requires a lot of text processing, via vim/perl.

I wouldn't know if using a scroll wheel is faster, I use terminal vim exclusively because I am working on a cluster and that's the best option (vs gvim). Usually use keys that do something similar to the page up/page down keys. That, or jump to top/bottom of file, which I use a lot and is certainly faster for me than a mouse would be.

I have never used IDE editor shortcuts, except for save, find, zoom in/out, and compile I think. For one, I don't use any other shortcuts frequently enough (that I notice) to remember them, for two, they aren't particularly easy to remember. F5 is compile and run you say? Cool. It would be nice to rebind that to :cc if I had the choice.

Overall, I don't think I will be convinced that an IDE can help me (or most vimmers) edit code faster. I mean, it's not like I haven't used them. I think, if you are writing a lot of different languages, or even just editing text files of data, especially sequentially (edit makefile -> edit shell script -> edit perl file -> run make -> edit makefile -> run make -> edit output file), then vim is your friend. If you want to write a large commercial program possibly not. Debugging? Probably not. Viewing waveforms? Certainly not.

→ More replies (3)

18

u/sillybear25 Oct 04 '13

Just use oranges (instead of apples)

Sublime Text is a GUI editor designed for local use. Vim is a command-line editor optimized for use over a (potentially slow) remote connection. As a result, the goals, paradigms, philosophies, etc. of the two editors are very different.

Using a GUI text editor (such as Sublime Text) over a remote connection requires X-forwarding, which can be quite slow even with a decently-fast connection. When your interface doesn't respond in real time, it doesn't matter how easy it is to navigate menus or remember keyboard shortcuts; your overall work speed is limited by the interface response time.

With Vim, there's no need for X-forwarding because it doesn't have a GUI. Furthermore, it was developed in a time when it was common for even a command line to have noticeable latency. Since said latency occurs with every keystroke, Vim's goal is to do as much as possible with as few keystrokes as possible.

I have nothing against Sublime Text; I'm just trying to demonstrate what happens when you compare two things on their ability to do something that only one of them was designed to do.

tl;dr: Use the right tool for the job. It doesn't matter how great Sublime Screwdriver is when what you really need is a wrench.

3

u/[deleted] Oct 05 '13

Can't upvote this enough.

I've been puzzled since the start of this 'vim vs sublime' wars, why are these two things being compared??

There is a reason sublime can do a bunch of stuff vim can't.. hint: native desktop client. And there have been IDE's around for decades who do a way better job then this 'just another text editor with plugin support'.

The only thing sublime is replacing in my workflow is notepad++, so it would be great if these 'bloggers/fanboys' would concentrate on comparing these two editors in the future and leave vim alone.

9

u/[deleted] Oct 04 '13

"You need to keep vim in your head"? I don't know about this claim - although I've been using vi since before there was vim, so I've internalized a lot of it. But once I got over the hump, vi just "disappeared into the background", even more so than any IDE I've ever used.

5

u/nairebis Oct 28 '13

No software tool I've ever used has disappeared and let me work as if it's an extension of my mind than Vim. If you never have to look anywhere else except at your code or a single line at the bottom for text commands, then that text editor has succeeded at its function.

48

u/ifonefox Oct 04 '13

I was hoping for in unbiased comparison. I did not get that.

4

u/superpowerface Oct 04 '13

He must've been drunk, it says so right at the top.

3

u/joerdie Oct 04 '13

I too was hoping for this. I am in my first year as a programmer and did not want to continue using the IDE's I was told to use in school. (Mainly because I am told they suck but no one can ever tell me why...) I have been tinkering with Sublimetext but it seems weak to me. I was wondering if I was missing something. I still think I may be...

6

u/MediumRay Oct 05 '13

I guess the funny thing about vim/emacs/etc. is that if you want to test them out, it's going to take quite a while of trying it before you realise what people were yapping on about.

1

u/joerdie Oct 05 '13

I agree with you. I have been only using Sublime Text for two weeks or so. The issue I am currently having is that is slows me down. My old IDE had something like intellisense that made my life much easier. It also had a feature where, when writing the tag for an image, it would go get the height and width of the linked image for me. So I would write, "<img src="URL" height=" and it would auto populate the height. Same with the width. This kind of thing saves me a fuckton of time and I really miss it. I have given Sublime one month of full time use before I move on. I may try VIM as well but I have a feeling it will be too bare bones for me.

3

u/MediumRay Oct 05 '13

I don't know about sublime text, but if there isn't a plugin for vim you can install to do that, you can probably write it fairly easily (well, I could at least). There's probably a whole bunch of great plugins for html etc., a lot of vimmers seem to be people doing web based programming languages. Vim is extremely bare bones to start btw. The point of it is you customise it as you wish (and fairly easily I would say), so you start with just the command keybindings. I hear you can do even more powerful customisations in emacs.

1

u/ryan1234567890 Oct 05 '13

The issue I am currently having is that is slows me down.

but,

if there isn't a plugin for vim you can install to do that, you can probably write it fairly easily

1

u/MediumRay Oct 05 '13

I don't see any juxtaposition there. If you want your editor to auto-populate your tags for you, and it's as easy as going to your configuration file and writing 'if prev_text == "IMG=" then insert $height, that's not really a problem. Easier yet, you can probably ask on the vim subreddit or mailing list and someone would give you it.

I often write functions while at work to speed up what I am doing, or, better yet, record a macro which you can then deploy as you wish.

9

u/brtt3000 Oct 04 '13

Sublime Texts is a pimped-up text editor, not a real IDE. But it has strong fanboy following (like vi and emacs).

2

u/[deleted] Oct 05 '13

FWIW, I recently traded in sublime for emacs, and have been very pleased with the result. Steeper learning curve, for sure, but well worth the effort. In my experience so far, very few of OPs complaints about vim apply to the build of GNU Emacs 24 I use (it is very easy to change key-bindings, emacs-lisp is just a lisp and lisp is widely used, documentation is robust both in emacs and online, there are minimaps and popup dialogues, helm-mode offers everything that the command palate does and more etc.).

1

u/joerdie Oct 05 '13

Are you using emacs on Windows? My work PC runs Windows 7 and I have heard that getting emacs running correctly in Windows is a bit of a pain.

2

u/[deleted] Oct 05 '13

Nope. I'm on OS X. But it looks like installation on Windows 7 might be fairly straight forward (for some, at least): http://www.claremontmckenna.edu/pages/faculty/alee/emacs/emacs.html

1

u/Meava Oct 04 '13

I agree with /u/brtt3000. But it is also a very fast and very powerful text editor. And unlike vi, you only need to learn a few keyboard shortcuts to take advantage of the advanced editing features. Btw, you can even make it an IDE, you just need to install the plugins you need, and Package Control makes it stupid easy to discover and install them. There are plugins to integrate with version control, build systems, to do static code analysis, syntax highlighting for niche languages, etc. I'd encourage you to take another look.

0

u/IneverSaidThat Oct 04 '13

I was wondering if I was missing something.

I think so.

91

u/frezik Oct 04 '13 edited Oct 04 '13

Just use {whatever text editor you know best}.

Edit: nobody should be downvoting any response by anyone in the thread below. All the discussion here is perfectly reasonable. (Except maybe the "This!" response.)

45

u/vanderZwan Oct 04 '13

The article is about what text editor to recommend to someone who is just beginning, so that argument doesn't really fly.

30

u/ogtfo Oct 04 '13

Someone who is just beginning should not be using vim, he should focus on learning the language, not the language and the editor.

6

u/Gudahtt Oct 04 '13 edited Oct 04 '13

"Beginner" isn't very specific; they could be months along in their learning. They could be working on a sizable project. At some point, a beginner is going to want to invest time into setting up a decent editor, and learning how to use it efficiently.

Trust me, it's important. I've seen people in a second/third year computer science program using notepad and Microsoft Word for writing code. Using a decent editor is worth the time it takes to learn how to use it.

8

u/[deleted] Oct 04 '13

What kind of CS program would let any 2nd+ year student think Word was OK for programming?

2

u/Gudahtt Oct 04 '13

They got a handful of suggestions during the labs, but they were all for linux (the lab machines use linux).

Occasionally, certain professors will talk about software recommendations for Windows, but it's uncommon. It's certainly not part of any curriculum.

10

u/ogtfo Oct 04 '13

I think we're both saying the same thing, but I'll will rephrase my opinion just to be sure. Choosing a good editor is crucial later on, but for a truly beginner I would recommend to either :

  • Use the editor that is bundled with the language (if there is one), or

  • Use an editor that will not get in your way. It can be powerfull, but it shouldn't come with a learning curve before you can even write in it. ie : notepad++ good, Vim bad.

Once you're familliar with a language, then you can reevaluate your needs and pick an editor, but it's useless to do this when you don't really know how to program, since you don't know yet what you need!

4

u/Gudahtt Oct 04 '13

Oh, yes, we are definitely saying the same thing.

Thanks for clarifying.

3

u/[deleted] Oct 04 '13

A text editor is one of the most important tools for any programmer. A new programmer should learn to use a text editor before learning a programming language. Preferably a text editor that can itself be programmed, like emacs.

16

u/ogtfo Oct 04 '13

Way to make sure nobody learns programming.

"Ok, so I know you'd like to learn to code, but first master this complicated and cryptic command line text editor with an incredibly steep learning curve, and then we'll talk. What's that? You don't want to code anymore?"

I'm not arguing against Vim or Emacs (I use vim extensively in my daily job), I'm simply saying it's not a beginner's tool. You start with the easy stuff and build on it.

→ More replies (3)

0

u/a31415b Nov 11 '13

anyone recommend vim for beginner should taken behind the bush and @()&&^

6

u/day_cq Oct 04 '13

MS Word/Excel is the best IDE

11

u/pohatu Oct 04 '13

Honestly, for a beginner, stock vim is just as bad if not worse than stock word. Word will get in your way by formatting your text as if it were prose instead of code, but stock vim will behave so unintuitively that the beinner using word will fly past the beginner using vim who can't get the fucking backspace to work.

14

u/[deleted] Oct 04 '13

To an extent. But UI is not just habit. Terrible UI can be tolerated through habituation, but that doesn't mean it's a sustainable or even optimal practice.

1

u/TKN Oct 04 '13

Since by "terrible UI" I automatically assumed you meant non-emacs editors I'm just going to go with /u/fresik s recommendation; use whatever you know and suits you best. When it comes to UIs we are all willingful victims of habituation.

→ More replies (2)

8

u/colinodell Oct 04 '13

Personally I'd rather use an IDE than a text editor, but your point is still valid.

12

u/frezik Oct 04 '13

I work on way too many remote servers for an IDE to work. I'd rather use a bunch of tools that I can configure into something that's 90% of the way to an IDE, but works over a terminal session and without the memory overhead.

3

u/[deleted] Oct 04 '13

I'd say the network overhead is far more relevant than the memory overhead.

2

u/frezik Oct 04 '13

I think you're overestimating the bandwidth needed for mostly-plaintext editing. Even with lots of terminal control characters and utf8, 2400 baud more than enough.

1

u/brtt3000 Oct 04 '13

Memory overhead an issue? In 2013?

31

u/okmkz Oct 04 '13

See also: eclipse

13

u/djchateau Oct 04 '13

There is a really disturbing trend these days with attitudes about memory overhead. Sure, we have more access to memory than we did before, but why the hell are we accepting these massive resource sucks as ok just because some people can afford the extra hardware? Maybe I'd like to run a low-resource machine on the cheap and still get my work done. Why do I need to load so many damn things because an IDE is trying to do everything under the sun short of making my coffee?

9

u/brtt3000 Oct 04 '13

If you want the productivity features offered by these IDEs then you have to pay for them, mostly with memory.

Most people work on beefy development workstations, because that is where you get the highest productivity (measured in real work done per hour).

And hardware is cheap compared to human time. I gladly loose 400mb of memory for safe re-factoring or member usage analysis. A stick of RAM costs as less then an few human hours of debugging: so if you don't mess-up one manual project-wide member-rename (because your IDE knew all the references and did it for you) you earned your memory costs back.

If you want to be cheap then you save direct money but pay for it in lower productivity (by having shitty code or burning time on manual search/replace refactoring).

You could try some plugins or scripts to do what a IDE integrated but then waste time finding them, getting it to work and risk all kinds of hell, instead of clicking somewhere, hit Refactor > Member and thumbing through the preview window and hitting OK.

2

u/FilipeArcanjo Oct 15 '13

Your post implies that to get those fancy IDE features you need tons of RAM just like eclipse requires. I don't believe that is the case. There are many reasonable IDEs out there (xcode, QtCreator and so on) which are not nearly as a memory hog as eclipse. And they do deliver most of its features. So... while RAM is cheaper then human time, not having to buy expensive hardware and getting the same set of features is even better.

2

u/brtt3000 Oct 15 '13

Yes, but Eclipse is of course notorious for being very heavy on memory (we used a Enterprise level AS3 plugin). Worth every byte it hogged though.

The projects where it got extreme were also the kids of massive projects you can forget about doing in a pimped out text editor anyway.

But now we're just discussing the merits of various different IDE's. I'm very pleased with my WebStorm, I cannot imagine going back to Sublime, it is a real step back.

But I think we can agree the IDEs in principle have proven their worth over text editors.

1

u/djchateau Oct 04 '13

If you want the productivity features offered by these IDEs then you have to pay for them, mostly with memory.

I definitely disagree with that assessment. I think it's quite possible to be productive and get the features you need without be wasteful in resources. The reason most people have beefy development workstations is not because it yields higher productivity necessarily but because we've accepted that we need to load a ton of stuff we most likely will not need during coding. The fact that a plug-in or script can very well replicate the same results as an IDE speaks to the idea that these IDEs that people use are bloated. You say RAM is cheap, but that's easy to say if you're not paying for it or you have easy access to spend money on hardware on a whim.

On a personal note, I don't like IDEs in general because it feels like it masks a lot of what's going on underneath and makes some programmers lazy about the code they write which itself can lead to time wasted refactoring simply because they didn't actually watch what their IntelliSense provided for them.

→ More replies (7)

5

u/frezik Oct 04 '13

Yes. Running three different browsers, one of which has at least a dozen tabs open, plus SQL Developer and a few other things, takes up some RAM.

1

u/[deleted] Oct 04 '13

Why are you running SQL developer on a remote server?

EDIT Never mind that doesn't make sense. Why not just buy some more ram for your desktop?

2

u/frezik Oct 04 '13

Why should I buy more RAM for my desktop when Vim in a terminal does everything I want it to?

→ More replies (2)

1

u/[deleted] Oct 05 '13

Maybe when memory comes down to $0.02/terabyte someone will put it together that the whole server won't actually grind to a halt if you start X daemon on it.

1

u/General_Mayhem Nov 24 '13

What IDE do you use that can't work over SFtP or similar? Emacs can do it with Tramp, Eclipse can do it with the built-in Remote System Explorer, VS has some sort of remote-view capability that works on MS-specific stuff.

1

u/rjbwork Oct 04 '13

Depends on your OS, but for windows a combination of Visual Studio/NetBeans + WinSCP allows me to automatically propogate changes to a folder and it's subfolders to the same location remotely. If you really wanted to, you could then set up a custom command button in VS (dunno about netbeans) to compile your project remotely or run any other build script you need to.

-1

u/brainflakes Oct 04 '13

Why edit over a slow terminal session when you could bring the file down to your local machine to edit it?

5

u/frezik Oct 04 '13

Because I have cable Internet, not a 56K modem.

For that matter, 2400 baud is far faster than you can read plaintext, so I'm not sure where you're getting the "slow" part.

2

u/Harkins Oct 05 '13

In the BBS days, 2400 baud was actually the speed I read at. And I regularly find remote vim over slower links than that to be quite usable when I'm dealing with network problems and overloaded servers. So I agree with you, but maybe it's time I start grooming my greybeard.

-1

u/brainflakes Oct 04 '13

Slow is a relative term, i.e. too slow (or limited resource I suppose) to run a graphical IDE on it.

So, why edit over a terminal session rather than download the files locally or access the files over a network filesystem? (I'm assuming the files you're editing would benefit from an IDE as you mentioned you'd like to get 90% the functionality of an IDE)

3

u/frezik Oct 04 '13

It's an extra step. I have to run the code on the web server, anyway, so why copy back and forth for every change? Plus, my vim config has grown organically to my style over the years; it's not a modular component that can be swapped out for something else.

2

u/rackmountrambo Oct 04 '13

Because most people don't cowboy edit on the live server. A deployment strategy will save your ass many times.

3

u/frezik Oct 04 '13

That's not what I do. It's a development server.

→ More replies (4)

2

u/[deleted] Oct 04 '13

I agree if the IDE is in emacs. Otherwise you think I'm going to learn a whole new set of editing commands for each new language I want to try? No thanks.

2

u/bastibe Oct 04 '13

For beginners, I totally agree. They have enough on their plate with learning how to program and such. They don't need to be further distracted with weird new writing tools.

For more experienced people though... As a programmer, you should really learn a programmable text editor. If programming is what you do, it makes sense to use tools that let you leverage your skills in order to improve your work environment.

Furthermore, you should really learn a powerful text editor well. Even if doing that only saves you a couple of seconds a day, your text editor is the one program that you will spend the most of your time using, so even pretty substantial learning efforts are still worth it in the long run.

2

u/superpowerface Oct 04 '13

Maybe it's just my limited experience, but isn't it the case that a good programmer shouldn't need to perform complex text manipulation gymnastics in their editor? I think that makes the points in the blog post moot.

All I need from my editor is syntax highlighting and search/replace, most of the time. Autocompletion and language-specific programming stuff is a bonus, but I leave that up to an IDE.

I use vim, just because it's installed everywhere and I ssh a lot but I've used nano, notepad and whatever else because I've just never required that much esoteric functionality.

17

u/frezik Oct 04 '13

A programmer most certainly will do complex text manipulation in an editor. Vim and Emacs and all the rest wouldn't be as internally complicated as they are if that didn't happen all the time. Almost all their features were the result of some programmer saying "I wish I had an easier way to do x right now", and then coming up with a method for x. Have that process iterate for a few decades, and you have Vim and Emacs.

2

u/bastibe Oct 04 '13

This is maybe the most concise explanation of why Vim and Emacs work the way they work I ever heard. Thank you!

2

u/superpowerface Oct 04 '13

The only time I've had to use complicated vim sequences is reformatting a badly formatted latex file.

What I meant is you don't really do complex text manipulation when writing code (I can't think of any examples) but almost exclusively for something like reformatting or editing datasets.

1

u/frezik Oct 04 '13

I'm not sure what you'd be getting at then. Lot's of text editors have Perl-Compatible Regular Expressions (for some definition of "compatible"), which can do very complicated things. Other than looking like line-noise, I've never heard of anyone saying this was a bad thing.

Some of the Lisp IDEs can fully parse the language, which means the editor can manipulate the code in ways similar to an optimizing compiler. Things can get really complex there.

3

u/Silhouette Oct 04 '13

Maybe it's just my limited experience, but isn't it the case that a good programmer shouldn't need to perform complex text manipulation gymnastics in their editor?

I've spent much of the last week converting the back end code for a medium-sized web application to use different date/time conventions, aptly enough using ST2 as my main editor.

I would give a lot right now for a static type system and the kinds of testing and refactoring tools a good IDE can offer for languages that have one. Dates and times are a messy enough subject in good languages with powerful IDEs. It is no fun at all trying to manipulate this kind of code as raw text in a general editor, even a decent one like Sublime.

1

u/ogtfo Nov 11 '13

Every programmer will have to do some refactoring now and then, and a powerful editor will make that job a lot easier. But even while writing basic code, I use vim's advanced features daily.

-11

u/musicmatze Oct 04 '13

This!

And for me this is vim. I don't get the point of this graphical stuff...

27

u/jfredett Oct 04 '13

"I don't like this, so you shouldn't either."

What an atrocious article. If you don't like vim, don't use it. In the meantime, those of us who do like vim will continue to use it, and be significantly happier than those people who don't like vim and are still using it.

I've been using vim since I was 8. I've used emacs (didn't care for it), I've used Textmate (what a terrible experience that was), I've used Sublime Text and I've used half a dozen other editors which I ultimately didn't like, but I also didn't hoot and hollar about how terrible those things were (except Emacs, but mostly as a joke, seriously, elisp = awesome, it's everything else I can't stand. :) ). The goal shouldn't be to discourage people from trying new things, the goal should be "Try Vim, Try Sublime, Try Emacs, Try M-x Butterfly mode. Try everything." This article is just another bit of detritus that does nothing to help anyone.

Big fat downvote, to match the ones I'm probably going to get for this comment.

5

u/joesb Oct 05 '13

"I don't like this, so you shouldn't either."

More like "I don't like this, so I wouldn't recommend it to you". Does that sound bad? Or do you always recommend things you don't like to people?

6

u/jfredett Oct 05 '13

That's not the tone of the article -- the tone of the article is 'Let's hollar about things I don't like about vim, and then list a bunch of things about Sublime Text that are basically orthogonal to the things I don't like, and build an argument that vim sucks and you should use Sublime Text 2 instead.'

See, here's the thing -- I do recommend that people check out things I don't like. Heck, even I check out things I don't like from time to time, just to make sure I still don't like them. I used to be a big firefox guy, didn't like chrome, then I tried chrome and found that I liked it, so I used that. I used to not like Node.js. I still don't like node.js, but I have recommended people try it, if only to see how terrible it is. Do I always recommend things I don't like? No, but I also don't go around telling people they shouldn't use things just because I don't like them.

Furthermore -- it doesn't matter if I fall victim to the same mistakes this article makes, tu quoque is a fallacy, it's still bad-thinking to make that "I don't like this, so you shouldn't either" argument.

So, in conclusion -- first, I think that you're misrepresenting the tone -- though frankly I could be just as well; we can only make guesses about what the intended tone was, and only make assertions about what tone we inferred. Second, I would say that -- most of the time, I don't make the same mistake as I think the author is making, but it's not unlikely that I've done so in the past. Finally, even if I (or you, or anyone) did make that mistake, it doesn't mean it's not still a mistake, and ultimately detrimental to the community as a whole.

Thank you for raising a good point though, discussion is always good for everyone, I think.

3

u/_FallacyBot_ Oct 05 '13

Tu Quoque: Avoiding having to engage with criticism by turning it back on the accuser - answering criticism with criticism.

Created at /r/RequestABot

If you dont like me, simply reply leave me alone fallacybot , youll never see me again

→ More replies (4)

1

u/TheNosferatu Oct 09 '13

It's a shame you read something else completely than me, he wouldn't recommend something based on X and Y reasons.

This article seems to be aimed for beginners, to which I would agree, I have seen some very nice things when looking over the shoulder of (what I suspect to be) an expert VIM user.

You seem to like VIM a lot, would you recommend it to somebody who is thinking to himself 'gee, I should start programming in this language I've vagualy heard of!'? If so, I would love to hear your arguments as to why :)

5

u/vanderZwan Oct 04 '13

I wouldn't mind a simpe to install, modernised spiritual successor to ACME - when it comes to combining mouse input with text editing it seems to be an amazingly well designed interface.

Russ Cox' screencast of ACME

2

u/Marzhall Oct 04 '13 edited Oct 04 '13

After being a long-time vim user, I recently started fooling around with plan9, which lead me to acme. While there are times I miss features of Vim, I actually prefer acme to vim when on my Plan9 machine ( there is a vim binary in the "contrib" user-packages directory). I've found myself at work using visual studio and motioning to use a mouse chord or on the command line in Linux trying to edit a mistyped command instinctively. There are certainly merits to these features, and I'd like to see a marriage between them as well.

16

u/petulant_snowflake Oct 04 '13 edited Oct 04 '13

First off, vi (and its derivatives, ie, "vim", collectively written herein "vi") is not a text editor. vi is a text programmer. vi's learning curve is almost 0 if you come into vi with knowledge of, and understanding of advanced programming concepts. If you are learning to program and learning to use vi at the same time, you're going to have an even higher, combined learning curve. I do not recommend to novice programmers to start with vi, just as I do not recommend to novice drivers to learn to drive with an F1 car.

To use vi correctly, one should understand the following programming concepts: how stacks work and function, conditionals and functions, and truly understand and comprehend regular expressions. Comprehension here means being able to fluently read and write regular expressions -- on a related sidenote, for which I could write many many lengthy essays about -- too many programmers claim to "know" regular expressions, but cannot even write/read a basic regex.

I use vim daily. Strike that, I use vim hourly. I can guarantee you that the fastest Sublime Text programmer will not be faster than me in vi -- and I'm not even that proficient at vi compared to many others! Why would I be faster? Because I don't move my hands back and forth between the keyboard and the mouse -- not because I can't -- but simply because I don't need to. But that's not even the real advantage of vi. vi exposes so many other things to the user, that I couldn't even begin to competently list them all here.

Having worked in numerous pair programming teams -- often paired with those who are masters at programming, but stuck in the Sublime Text or IDE world -- the most common comment from a paired programmer when sitting next to me is "oh my god, how did you do that?" The answer is always "vi, man, vi." If you are having trouble understanding or visualizing how this might occur, let me put it this way: I can refactor millions of lines of text, spread across tens of thousands of files in seconds. And here's the kicker: that refactoring will be correct. This is not because I am an overly gifted programmer, but because I am programming the text -- I'm not editing it. If there is one tool that I would say has made me a better programmer, it is using vi.

If the guy thinks "20jFp" is the pinnacle of vi, then I can assure you that even after 4 full years of use he does not know how to use vi, and likely has not bothered to learn vi beyond even the most basic of cursor movements. He has scratched a nanometer into the surface of a 20 kilometer tall iceberg. For example, what the author here thinks is vi's pinnacle, ie, "20jFp" (go down 20 lines, find (backwards) 'p'), is the equivalent of moving the fucking mouse cursor. Hate to break it to you, but vi supports mouse cursor movements. I'll wager that the author didn't even know that.

You can use vi just as you would a normal text editor, with menus, and mouse movements, and all that -- ie, as a simple text editor, with great regex support. Personally, I use vi from a console terminal, but I wouldn't fault anyone who uses vi like this, in the same way that I wouldn't fault the author for preferring Sublime Text -- because vi's strength isn't in the fucking cursor movements. That's just one (albeit, a large one) aspect of vi's strength.

I leave this comment here, not to try to prove that vi is a better text editor (it is), but in the hopes that if there is someone who comes here who wants to master the craft of programming, then in some small way, I hope that I have cleared some of the damage, bullshit and otherwise FUD laid down at the hands of this know-nothing blog author.

For those wanting to master the craft of programming -- ask yourselves this: of the greatest programmers who have ever lived -- the Linus Torvald's, the Ken Thompson's, or the Dennis Ritchie's of our world -- do they use Sublime Text? No? They use vi or emacs? Understand, that doesn't just happen in a vacuum.

(btw, for the record, emacs is equally as good as vi. Personally, I'm a vi guy, but ymmv as they say).

3

u/[deleted] Oct 05 '13 edited Oct 05 '13

I'm a (relatively new) emacs user, recently graduated from sublime. The paradigm you articulate here of programming text is very illuminating. This is an excellent point you make: the power of the tool doesn't lie in how quickly it lets you move the cursor around (although, using ace-jump-mode in sublime (based on vim's EasyMotion?), I can jump directly to any word or character in 2-3 key strokes). It helps me understand why I haven't missed sublime's slick multiple cursor feature (I haven't even bothered to add the multi-cursor package for emacs): my composition process has become more programmatic, which means I have less need for a tool to help me manually correct manual errors.

Gets me psyched to dive deeper! Thanks.

-1

u/[deleted] Oct 05 '13

I use vim daily. Strike that, I use vim hourly. I can guarantee you that the fastest Sublime Text programmer will not be faster than me in vi.

Why is this a thing that anyone cares about. Why are we optimizing for editing text 10% faster? Moreover, ST3's better plugin system would undoubtedly crush you in many cases.

I can refactor millions of lines of text, spread across tens of thousands of files in seconds.

VS++ and IntelliJ do this better- thats exactly what they were built to do.

He has scratched a nanometer into the surface of a 20 kilometer tall iceberg.

This is the biggest reason why people don't want to use Vim. They just want to edit some text, not be forced to learn the equivalent of an iceberg.

For those wanting to master the craft of programming -- ask yourselves this: of the greatest programmers who have ever lived -- the Linus Torvald's, the Ken Thompson's, or the Dennis Ritchie's of our world -- do they use Sublime Text? No? They use vi or emacs? Understand, that doesn't just happen in a vacuum.

Are you really suggesting that because, Linus uses your editor, you are a better programmer?

I leave this comment here, not to try to prove that vi is a better text editor (it is)

I agree that Vim is probably the fastest way to change text in a single file in most cases after decades of use.

emacs is equally as good as vi.

Emacs is actually poor at editing text, although it has a sane plugin system if you understand elisp.

1

u/petulant_snowflake Oct 05 '13

You completely missed the point of my post. VS++ and IntelliJ don't work for all languages, now do they? I can refactor a million line Ruby, Shell, C++, C, C#, Scala, or any other language just as quickly with vi, irrespective of the language. It's because I'm programming the text -- I am not editing the text. One does not learn vi to learn how to edit text. If you want to only edit text, then, please, by all means, use whatever editor you feel most comfortable with. If you want to learn how to program text, then you need to start with vi, or something a lot like it (emacs).

With regards to the comment about Linus and other great programmers -- No, I am not so retardly stupid or conceited as to believe that because someone else uses some tool, then if I use it, then I am magically just as capable as them. However, great artists have their tools. Could you write the Linux kernel in Sublime Text? Yes. Does that mean that that's the best tool for that job? No. Vi is, by leaps and bounds, the best tool in general for programming text. Thus, it is the best tool in general for writing code. I might suggest that Sublime Text might be the world's greatest text editor. I don't know. I haven't simply edited text in a very very very long time to be able to proffer an opinion in that area, because I stopped editing text about 15 years ago. Now, I program text.

11

u/brainflakes Oct 04 '13

But, for software development, why pick Sublime over an IDE?

7

u/Guvante Oct 04 '13

Some people don't like IDE's for various reasons, typically the VIM crowd isn't interested in the IDE experience.

5

u/MediumRay Oct 05 '13

Or, you configure vim to be an IDE, or use a vim keybinding plugin to your IDE. Win-win.

1

u/xwz86 Oct 05 '13

Or configure your IDE to become vim.

4

u/MediumRay Oct 05 '13

Isn't that the same as using the vim keybinding plugin to your IDE?

3

u/xwz86 Oct 05 '13

Honestly, I just replied as a joke :) Although I was referring to the plugins for Visual Studio and IntelliJ, vs: Vim with all of the plugins that would literally make Vim into IDE. You are productive either way, but I don't consider Vim + 50 plugins, or Sublime + 50 plugins, just a text editor. IDEs are just text editors with plugins if you think about it.

2

u/MediumRay Oct 05 '13

I think I agree. A lot of people say that you shouldn't turn vim into an IDE for whatever reason. I say meh.

Have you used the Visual Studio plugins etc.?

→ More replies (2)

3

u/eikenberry Oct 04 '13

Because some people use a flexible IDE where you can swap out parts like the text editor.

2

u/mondoman712 Oct 04 '13

UNIX is my IDE.

1

u/loluguys Oct 05 '13 edited Oct 05 '13

IDE's always have felt far too clunky for me. 95% of the 'features' are things I don't even use, and are just a distraction and eyesore. (Of course, you can hide them, but that's just throwing your trash under the bed.)

1

u/dacjames Oct 07 '13

Multiple editors. I've never seen an IDE that supports the kind of text editing functionality the Sublime (and Vim) does.

1

u/brainflakes Oct 07 '13

I've never seen an IDE that supports the kind of text editing functionality the Sublime (and Vim) does.

Can you give an example of those features? I'm genuinely interested.

1

u/dacjames Oct 07 '13

Multiple editors allow you to edit more than one location in a file simultaneously, which can be extremely efficient.

Let me give you a real world example: recently, I had to write a parser for the data files from the census. They use an archaic, fixed width header format, the spec for which is embedded in a PDF document. I grabbed the text for the spec from the PDF, in the form of a text table. Using multiple editors, I worked on all the rows at once, transforming them into a Python dictionary that my code could read.

I could do all this with regex find/replace, but that's slower and more tedious. Multiple editors allow me to do everything from renaming variables (or changing parts of variable names) to transforming CSV into JSON. It's addicting and hard to give up once you have it.

Sublime has a lot of features that make working with text easy and fast (e.g. join lines), but multiple editors is the most important.

→ More replies (1)

0

u/[deleted] Oct 05 '13

The first time I used Intellij, it literally took me 30 minutes to figure out how to edit a file. As in, open it up, change it, and save it.

Another answer that few will admit: Sublime is far and away the sexiest editor around.

→ More replies (5)

57

u/[deleted] Oct 04 '13

Sublime Text is proprietary. No thanks.

7

u/SomethingMoreUnique Oct 04 '13

I'm genuinely curious: why does that make it bad? I paid for and use IntelliJ IDEA for Java because I feel* it's leagues ahead of the free and open source IDEs.

*I'm not trying to start a Netbeans vs. Eclipse vs IDEA war here. Personally, I prefer IDEA. For some, Eclipse is the best. For others, it's Netbeans.

9

u/[deleted] Oct 04 '13

It's not bad, it's just not for me. I don't like depending on someone else's business model for my toolchain.

3

u/[deleted] Oct 05 '13

But you will always depend on someone else's business model: from your computer and the power to run it down to your food and how you get to work. It's the economy, we are all interdependent.

2

u/wmil Oct 05 '13

It causes a problem because you have to worry about licensing whenever you need to install it on a new system.

Sublime Text's licensing is quite reasonable so it isn't usually a problem. But think about editors with strict licensing and online activation... Having a copy at home and work is a problem. Or installing it on a new system. Or starting a new job. Open source is just easier.

The other problem is that the makers of a proprietary editor can decide to change all of the key bindings at any point on a whim. Your only choices will be re-learning everything or avoiding updates and waiting for operating system incompatibility to happen.

Learning an editor is a big task and open source gives you some protection. There are still some XEDIT / KEDIT users out there who don't want to give up their macros.

2

u/mgrandi Oct 04 '13

because proprietary is evil!**

** says the guy who is probably running windows, mac os x, or linux with some form of binary blobs in terms of drivers/programs, need not apply if you are RMS

11

u/erez27 Oct 05 '13

Proprietary is something to avoid, if possible. Very few things are so important that they drown out all other considerations, but open source is definitely something I put some weight on.

-15

u/cheeeeeese Oct 04 '13

also full of bugs.

0

u/[deleted] Oct 04 '13

[deleted]

5

u/[deleted] Oct 04 '13

0

u/[deleted] Oct 04 '13

[deleted]

4

u/[deleted] Oct 04 '13

If you want to go by "all", then it is impossible for my code to all be open sourced. The early stuff predates both the 3-clause BSD and GPL 1.0. But then I don't have those old Apple floppy disks around anymore anyway.

14

u/[deleted] Oct 04 '13

[removed] — view removed comment

0

u/[deleted] Oct 04 '13

[deleted]

11

u/[deleted] Oct 04 '13

[removed] — view removed comment

0

u/mgrandi Oct 04 '13

try emailing the guy? I feel its just c++ so it should compile for ARM without too much trouble?

→ More replies (1)

10

u/alotofreddit Oct 04 '13

1-2 years seem like a lot of time to me. I needed several months to get comfortable with vim (not perfectly, but enought to work with it).

At least for me vim is not just about the speed of text editing. I enjoy it more to move around in the file using the keyboard than using the mouse (moving hand vs not moving hand). I don't know if I am faster but it less frustrating than moving my hand to the mouse every minute.

Also I love using vim commands outside the vim text editor. Many IDEs have vim-plugins (e.g. Visual Studio and Pycharm). It combines the capability of a 'real' IDE and the fast/comfortable editing of vim.

But I agree that the vim editor can be a bit frustrating/underwhelming in comparison to other 'modern' text editors (like sublime).

3

u/tias Oct 04 '13

Give it a couple of years. One day you'll say "woah, I've been using vim the wrong way all this time!"

2

u/MediumRay Oct 05 '13

I say that every five days. Especially since I am currently reading a book on editing vim well. I regret my early keymappings. Why did I think f and r were useless enough to be remapped?

1

u/[deleted] Oct 05 '13

After many years, I'm still learning new things about vim or some new plugin that blows my mind.

1

u/xwz86 Oct 05 '13

I use IntelliJ alot, with python and other plugins... However, I've not used Vim too much, although it's my go-to tool when I edit code remotely... Can you tell me if the Jetbrains plugin is good enough? Is it much better than the default text editor (in your opinion) ?

1

u/loluguys Oct 05 '13

Vim starting leaking for me as well... ending up switching to AwesomeWM, Vimium (Chrome add-on), and Zathura (pdf viewer) for some more key control.

My fingertips couldn't be happier.

13

u/kkrev Oct 04 '13

This guy basically says vim is a problem if you obsess over superfluous plugin functionality and endlessly dick around with plugin settings. Um, just don't do that. Who needs snippets and a file browser in the text editor? I don't.

3

u/Zamarok Oct 04 '13

Well I sure do. UltiSnips and NERDTree are great though.

1

u/dreucifer Oct 04 '13

I stopped using NERDTree, I have ranger open up files in an existing vim session.

-4

u/[deleted] Oct 04 '13

Heck, who needs syntax highlighting? Indentation? Who needs copy-paste? Who needs scrolling?

4

u/[deleted] Oct 05 '13

punchcards, dawg.

0

u/rs-485 Oct 04 '13

Vim supports all of that.

-3

u/Suitecake Oct 04 '13

whoosh.gif

→ More replies (1)

5

u/spupy Oct 04 '13

Huh, didn't know there's a new editor war going on. Should I grab the popcorn?

2

u/erez27 Oct 05 '13

We have always been at war with SublimeText

1

u/dreucifer Oct 05 '13

Lol, I don't think we started the war. We just suggest that people take the time to learn vim and suddenly there are SublimeText users coming out of the walls going, "BUT VIM ISN'T BEAUTIFULZ!!!21!".

1

u/erez27 Oct 05 '13

But it is...

1

u/dreucifer Oct 05 '13

Yes, but not padded, multi-sized, perfectly kerned text beautiful...

16

u/[deleted] Oct 04 '13

I bet this dude sucks at vim

0

u/[deleted] Oct 04 '13

[deleted]

4

u/[deleted] Oct 04 '13

Saying someone sucks at something isn't a reference to their potential, it's about how effective they are at that moment. Everyone who has never used vim sucks at vim, and if this guy didn't put in the effort to learn it then he probably sucks at it as well.

3

u/Tenobrus Oct 05 '13

Did you read the post? He says he's spent four years learning it. And that he wrote the post in vim because he couldn't stand using a normal text editor. I suppose he could be lying, but just because he disagrees with you doesn't mean he's incompetent.

6

u/Resquid Oct 04 '13

If you deploy and support the software you write (and don't simply run it locally) you'll eventually need to expand your skill-set beyond Sublime.

2

u/rackmountrambo Oct 04 '13

I don't get it. I build and support large web apps and sublime has been great for me.

1

u/misc_ent Oct 04 '13

I've used a lot of editors (including Vim) and love Sublime. It scales with me and my projects. I would also be interested to know what I would need to expand.

1

u/General_Mayhem Nov 24 '13

Yeah, you might need to go as far as Sublime over SFTP.

Of course, in the real world, once you scale to multiple boxes, your remote server configuration and management won't be done by hand in any sort of text editor or IDE, and the thing you'll need to add to your skillset will be bash scripts, Puppet, or something else actually meant for managing multiple machines.

6

u/nrith Oct 04 '13

tl;dr.

I honestly don't care a god damn what new programmers learn to use, or what experienced ones use already. However, if a programmer has at least a couple years of experience, I do think that they should be proficient in either vi(m) or emacs, just as I would expect them to know some advanced topics in their languages of choice.

0

u/neutronbob Nov 14 '13

Well, that's not exactly a tl;dr of the post. Let's say it's a tl;dr of your opinion of the post :-)

2

u/JKirchartz Oct 05 '13

Let's go blow-for-blow:

You Need To Read (At Least) Two Books On To Use Well

or practice, and learn new things as you need them; this way might take a little longer to "know" vim, but it's easier to learn by doing than by reading.

hjkl ... months of frustreation

or play vimsnake for a couple hours (the hard part of this is switching modes in time to turn away from a wall)

Efficiency from Keeping your Fingers on the Home Row

How long does it take to type 5 characters when your hands are on the home row, and how long does it take you to move your hand to the mouse? How long does it take to visually scan the file to find where you want to click? Gamers might have better experience with the mouse, but typists are going to be quicker on the keys.

Plugins and Extensibility

Plugins take a little lovin' to use; but really a plugin isn't going to help you use vim if you don't know how to use vim. Vim's a (mostly) command line tool; you have to be comfortable with operating in a terminal. A lot of the time vim plugins just rehash built-in functionality (NerdTree etc vs the Shell etc, (ctrl-Z & fg FTW)) Vanilla vim is bad, only if you don't understand vim.

the vimscript site is ugly, like it's been designed by C programmers and engineers ;), not long ago the entire internet looked like thok.org. Alot of vimscripts ARE on github, and if you use git & sub-modules they're very easy to keep up-to-date.

vimscript

On no! nobody knows vimscript! Only a small subset of vim users who make plugins! - plugins are nice-to-haves, not necessary features for a text editor. Also, it's not that different from existing languages, most programming uses the same underlying ideas & techniques, and each have their shortcomings; even so, vimscript (aka vimL) is the 14th most popular language on github.

collisions

45 plugins? Nobody needs that many, and if they don't work together don't use something else! Stop being lazy and learn what vim itself does, and choose a small set of plugins you will actually learn and use! If you don't use it, you don't need it, and if it's not installed it won't cause problems!

Vim Is Bad By Design™ 1: Oooooollllld

VIM is designed to edit text over a slow, unreliable connection, from a dumb terminal connected to a mainframe. You can remap leader to anything though, a lot of people use the spacebar for this because it's otherwise unused. Also you don't need :arglist to deal with multiple files, you can use :buffer to do it too. :buffers or :ls to show all open buffers, then you can switch with either the buffer number, or the buffer name (using the shorthand for buffer) :buff 4. The arglist is like a stable subset of buffers.

GUI

Yes, there's no "gui" taking up my screen; So when working remote there's no need to transfer image-data. Vim is a heck of a lot more powerful than pico, which is a gui-like editor in-so-much as it tells you what keystrokes perform which (basic?) functions. (Does pico do much more than it clearly displays? who knows, use vim)

vim bad at indenting

yes, auto-indenting of large blocks of un-formatted code; but why wouldn't you indent it when you wrote it? Or paste it in with paste-mode so the indents come with it?

After four years of Vim use, 700 hand written lines in my .vimrc, and 45 plugins...

Oh god! why!? This guy clearly never wanted to learn vim, but to bend it to his will. No wonder he had conflicts. I usually see people using 10 plugins max, and rarely does anybody need a vimrc with over 300 lines, 40 would be better. (mine's 201, but if I ever feel the urge, I'm sure I can remove a lot of it, because they duplicate default values)

having set -o vi in bash has been great, I don't need to learn new keybindings for quickly editing commands etc; also I find that if you edit your bash commands, sometimes it becomes impossible to edit the last character <esc>A fixes that.

TL;DR: VIM is part of a system, that includes the rest of the Shell/OS. They all work together, and can be used together efficiently. Vimscripts are written by a large(ish?) community, so fragmentation's expected. If you really want to use your mouse and the typical GUI experience try gVim or set mouse=a.

2

u/zeugmasyllepsis Oct 18 '13

Vim vs Sublime

Someone mentioned that they wished they'd seen a more decent, unbiased view of the two editors. I've used Sublime since the beta version of ST2, and I've used Vim for about 6 years now, on and off, and mostly use Vim now for development. I would consider myself a decent Vim user and a slightly more than casual Sublime, so I may be more biased towards Vim. So take that into consideration.

For Sublime

  • Vim package management needs help. I prefer to use Vundle, others prefer Pathogen. Either way, the official site of repositories sucks bigtime. It needs to be redone. Sublime Package Control is fantastically done; ctr+shift+p Install and I'm ready to search for the package by name. Unbeatable.

  • Vim users have to admit, it's pretty. Sure, Vim is meant for the terminal, remote editing, etcetc. But there's a GUI for it, there's no reason you can't use the GUI when doing local editing, and none of them look as nice.

  • Vimscript isn't that bad of a language, but it's another language and it's virtually unused outside of Vim. I'd prefer to use a language that I can reuse elsewhere.

  • This might be completely personal preference, but I like the keybinding syntax in Sublime much better. The <C-W> for control key plus lower case w is is very confusing to me; that looks like "capital c capital w". Similarly confusing, Ctrl-I maps to tab, Ctrl-[ to escape, Ctrl-M for enter, Ctrl-H for Backspace. Or <Tab>, <Esc>, <Enter>, <BS>. My point here is not that one syntax makes more sense than the other, but that Sublime keybindings are much more consistent. Even if there is more than one way to write a command, authors have generally stuck to a single format with a very readable syntax.

  • The Sublime command pallete is excellent; sometimes I just cannot remember the keyboard shortcut for something and don't really care to look it up. It might be something I use infrequently or it's bound to an obscure keybinding to avoid conflicts. Either way, being able to fuzzy-search commands is beautiful. Made even better by the (I think) convention of adding the package name before the command. What can I do with this new plugin I installed? Pull up the command pallete, type the package name, and see what commands come up.

  • Ctrl+p is just plain awesome. The syntax of prefixing @ or # to match symbols and words is beautiful. Vim comes close with plugins (I use TagBar and CtrlP), but doesn't quite get this good.

For Vim

  • Sublime's documentation is decent, but Vim's is downright astounding. The official Sublime documentation is downright embarassing. The unofficial is better, but I still found that I was having to work through how plugins worked a lot on my own or by asking other plugin developers. Neither of these come close to :help <command> in vim.

  • Vim's macro system is fantastic. The amount of time it can save when editing a file is hard to compare. Vim truely is a language for defining text transformations, and it works beautifully with macros. Sublime's Vintage mode has decent support for macros, but missing features and some slight differences in behavior make it less reliable, in my opinion. Yes I know Sublime has it's own macro system, but from my experience they are simply on different levels. I'd be interested in hearing stories about cool things people have done with Sublime macros; I suspect I'm not using them to their fullest extent.

  • Some plugins in Vim I haven't found a good alternative for in Sublime. I like being able to customize what shows up in my status line; Airline is perfect for that. Does Sublime have something similar?

  • Sublime isn't open source. I know this doesn't matter to some people, but to me it's a big sticking point for one reason: lack of documentation. I could forgive Sublime for not being open source if it had supurb documentation, but without either that OR the ability to read the source code I feel like I sometimes get stuck and don't know how to get out.

  • Even with Vintage mode on, there are some times when Vintage opts to map to base Sublime features where it loses power. For example, in Vintage mode, / brings up the default find bar, which means I now have to use the mouse to toggle things like case sensativity, regex, whole word, wrap around search etc. I'd like to be able to type something in the bar that pops up to avoid that.

  • I'm a terminal junkie. I know not everyone is, but being able to quickly run arbitrary shell commands without leaving my editing session is pretty awesome. Someone recently pointed out a plugin for Sublime, so maybe I just need to give that a try.

Both Awesome

  • As much as the packaging system in Vim is a pain, the ecosystem of plugins is absolutely fantastic. Similarly, Sublime's plugin community is fantastic. Both are winners here, and I think this is a good indicator of how flexible both editors are.

  • Editing multiple files in both is a breeze. Buffers/Tabs in Vim with a couple of plugins is a beautiful thing, similarly with tabs and ctrl+p in Sublime.

  • Both are pretty good for editing big files, with a slight nod to Vim for buffered reads, making it easier to work with massive files if you avoid operations which work on text outside the viewable area; things like automatically highlighting matches when searching.

Both Suck

  • Interactive editing. I'm a long time Python programmer and have used fantastic tools like IPython, which allow cell-based editing (executing, modifying, and displaying inline results for portions of the program). Let me be clear, I understand that neither of these editors were designed with this in mind, but it's something that I occasionally look to other editors for. I haven't looked into plugins for this yet. I see some decent looking ones for IPython in specific, but I'd like a more general solution for working with an external interpreter. This seems like the kind of thing emacs would be excellent at.

That's all I've got for now. Comments, suggestions, and discussion are encouraged! As I said, I love both programs and use them often. Just my thoughts!

1

u/codygman Nov 25 '13

The interactive editing part is a large reason that I switched to emacs recently. the other reason being I know lisps/schemes pretty well, and elisp is a very nice language.

I have around seven years of vim experience, and now about 5 or 6 months of the emacs experience.

1

u/codygman Nov 27 '13

The interactive editing part is a large reason that I switched to emacs recently. the other reason being I know lisps/schemes pretty well, and elisp is a very nice language.

I have around seven years of vim experience, and now about 5 or 6 months of the emacs experience.

6

u/CandyCorns_ Oct 04 '13

I've read several articles comparing Vim and Sublime Text 2, but never in favor of Sublime Text 2 until now. I'm very sad that this article is so very poorly written, because I was hoping for something to break away from the trend.

The author makes a large bunch of assumptions about the user, and how long it takes to be proficient. For myself, I noticed results in the first couple of months of Vim use, and I found that I could never go back. It certainly did not take two goddamn years to notice a difference.

1

u/dreucifer Oct 05 '13

If I hadn't been pointed to vimtutor and the :help command, it might have taken something like two years. Ten minutes in vimtutor and I was at the same level of proficiency as my coding in notepad (well, gedit or notepad++). Once you get some plugins installed, like tpope's surround, and you'll be loads faster. Learning grep and the argslist makes multi-file text-manipulation a snap. Then you're on to passing the buffers to programs for other simple things (want to sort a list alphabetically, just :%!sort. Got duplicates? :%!sort|uniq. Even works with visual selections and line numbers.).

2

u/MrDubious Oct 04 '13

I'm a guy who started out in telecom, and was very used to terminal sessions for maintenance. When I first started getting into programming, many of the tasks were performed using vi or vim on remote sessions to our AIX/SCO boxes. Being at the beginning of that learning curve, the top part (proficiency) very much seemed like an unattainable goal.

Then I was exposed to advanced text editors and IDE's, and it was like a light came on. Here was a UI similar to what I was used to, which featured things like syntax highlighting (oh my god, the colors) and beginning/endpoint detection. Suddenly, instead of struggling to learn the interface, I was actually focused on the code, with an application that was helping me along the way by making it clear and easy to read (and helpfully pointing out the missed line terminators).

I think that's his point; when you're a beginner (and I consider myself to still be fairly beginnerish after a few years of doing this, compared to the kid geniuses I see on here), working with vim feels like learning two languages at once, and is slow and painful. My functional knowledge increased a TON in the first year after I started using UltraEdit, because instead of searching "how do I insert a block of text in vim", I was searching for optimization methods, memory use, functional best practices...you know, the ACTUAL development stuff I needed to learn.

tl;dr vim is a powerful tool for a specific job, but really best used by people already proficient with the language. It's a terrible way for beginners to start.

2

u/logophobia Oct 04 '13

The vim keybindings are amazing, vim as an ecosystem, kindof meh..

My solution is to use full blown IDEs like visual studio or eclipse, then use addins like VsVim, Eclim, vrapper to integrate vim into your IDE. Instead of trying to make vim into an IDE with NERDTree and other plugins.

It means you get all the productivity advantages of both vim and an actual full-blown IDE.

1

u/xwz86 Oct 05 '13

Have you used the Vim plugins for any of the Jetbrains products, if so, how are they compared to vim itself?

2

u/logophobia Oct 05 '13

No, I haven't used any of those plugins

2

u/Superkargoeren Oct 04 '13

Once you actually learn vim you will miss it no matter what editor you use. That's my experience with it at least.

2

u/JollyRancherEater Oct 12 '13

As a programmer I end up going into and out of hundreds of files a day. In most cases I open a file to fix/modify/add a single line of code, or just to view it for a second or 2, then close it out. I feel bad for anyone who waits for some GUI based application to open their files.

1

u/Daniel15 Oct 05 '13

Why would I use Sublime Text when WebStorm is cheaper and does more?

1

u/thoth7907 Oct 10 '13

You need OSX and/or Linux, or aren't confined to JavaScript?

1

u/Daniel15 Oct 10 '13

WebStorm works on Mac and Linux, and you can get a specialised IDE (like PhpStorm) or IntelliJ which supports everything.

1

u/thoth7907 Oct 10 '13

Dang I'm blind, didn't notice the other tabs for the other platforms!

1

u/fmargaine Oct 08 '13

Most people don’t know about NERDTree tabs, but NERDTree is incomplete without it.

I don't know, am I the only one who never uses tabs?

2

u/JollyRancherEater Oct 12 '13

I untabify everything

... Except makefiles [learned the hardway]

1

u/fmargaine Oct 12 '13

I meant using tabs as in :tabnew.

1

u/shotxxxx Dec 16 '13

just use sublime text

Here. Have the just as old rebuttal post. https://sublimebullshit.wordpress.com/2013/03/22/response-to-andrew-rays-blog-post/

Sublime Text is just Textmate rehashed for clueless noobs in the hope to make a few quick bux.

1

u/eggomygriego Mar 04 '14

There is one thing that may be over looked with this discussion. I agree with using vim, although I am not very good, I can see how useful not using the mouse could actually be, but its not JUST using only the keyboard that makes vim powerful. As high as the learning curve is, if you were to master it, your productivity increases(in combination with tmux or screen) because your no longer tabbing in and out, your also testing, debugging, etc. If you live in the terminal than tmux + vim could be easily advantageous over using a program like sublime.

On the other hand, sublime offers vim plugins to allow your key commands in sublime to reflect that of vim, even insert and esc mode, which does give you the option of using the keyboard in sublime. So if thats the only part of vim that you see beneficial, than I would say do that, but there is so much more vim could offer as in terms of efficiency, not to mention that it comes preinstalled in every unix/lunix machine so if you know vim and something like tmux, than you can remote login to a unix machine and pickup where you left off, not really something you can do (easily) with sublime.

Just a few notes

-9

u/SrPeixinho Oct 04 '13 edited Oct 05 '13

NO.

Vim user for a year. Sublime is a toy for kids. Can't do half of what I do with Vim. Vintage mode is broken. You are just trying to make an excuse for going through the easier path.

Edit: gotta love the hurt chickens downvoting me! Even more when nobody came up with an argument. Just votes. Truth hurts, fuckers.

0

u/[deleted] Oct 04 '13

[deleted]

2

u/[deleted] Oct 05 '13

Can't speak for Vim, but in emacs I can do these things that i couldn't figure out how to do in sublime: run the shell in a buffer; arbitrary division of buffer panes (in emacs, 'windows'); proper Prolog support; built in documentation on any key-stroke or function, that includes a link directly to the place where it's defined in its source file. This last piece is a huge difference of course: in sublime you get access to a limited API, and support for json-based snippets and settings; with emacs-lisp, you can alter or extend any part of program in anyway you please. So the biggest thing I can do in emacs but not in sublime is write any arbitrary functions I want in my initiation file, extending or drawing upon any core or plugin features, to realize any functionality I can imagine.

2

u/[deleted] Oct 05 '13

Yes, the "shell in a buffer" is what I miss too. I mean it has a little pull-up window that can display build reports or in my case syntax errors when I work with SublimeClang.

I wish Sublime was open-source, that way it could have unlimited extendability.

2

u/[deleted] Oct 05 '13

I'm with you. Of course, Sublime is supported by a generous and ingenious community of contributors who have managed to develop quite a thriving ecosystem in any case. It would be great to see what they could do with unlimited access, but I also understand why the developer chooses to keep it locked down.

2

u/SrPeixinho Oct 04 '13

Macros and most of the key stuff. This is a video I've made to show one of those things. You could do THAT on Sublime, perhaps, with macros and some mouse deleting. But when it comes to anything more complex than that, such as reversing the order of the arguments of all the functions on your file... things like that, that you can do in a dozen keystrokes on VIM... well, good luck figuring out on Sublime.

But in summary, the fact I never remove my hands off base is what makes me so fast. Command line integration, macros, easymotion, hability to map the key "r" to <save, compile, refresh browser> and stuff like that help a lot. But mostly it is the "flow" mode you enter when you just type type type type and stuff happens and ba, you've just made a copy of megaman 3 in 5 days.

But you can't understand it before you are good enough on VIM. I admit. I couldn't.

→ More replies (3)

0

u/dhvl2712 Oct 05 '13

I think most people would agree that vim should not be used for large projects or by new users.

0

u/Elite6809 Oct 04 '13

Gedit's where it's at.

0

u/neurobro Oct 05 '13

Vim out of the box is awful. I can’t stress how bad of an editor vanilla Vim is. Plugins are essential to make Vim usable.

This makes me want to dig up some plugins and give it another chance. As it stands I've only learned enough vim to edit config files in an emergency. It just seems like it would be hellish to spend any significant time in that environment, but that could be because I never took the time to tweak it.