Tag Info

Hot answers tagged

62

The main reasons why I prefer a terminal-based editor over a full-fledged IDE: Remote access. I can ssh to whatever computer I need to be on, fire up Vim and start working away. In a day-to-day basis, using screen session and Vim allows for easy access from any location. Keystrokes. There are so many keystrokes saved once you can utilise Emacs or Vim to a ...


49

Programmers are notorious for using the tools that helps them get the job done in the most efficient way possible. These editors are ancient yet still being used because they are good, solid editors, proven by time. If they get the job done and get the job done well, why should we drop them in favor of something else?


48

When I read The Pragmatic Programmer and they suggested that one picks a text editor and learns to really use it, I chose Emacs and really I haven't looked back. I don't use it for everything- if I'm developing .net I will tend to use Visual Studio because it's all set up for it, but for most web dev stuff I find it more helpful than an IDE and the ...


47

The I: integration. A good text editor may be nice for writing code, but most of your programming isn't spent writing; it's spent testing and debugging, and for that you want your text editor to integrate with your compiler and your debugger. That's the greatest strength of an IDE.


41

You assume they don't evolve. Emacs continues to grow by leaps and bounds; and, while vi was getting kind of hoary, Vim has rejuvenated it and if anything it's growing (feature-wise at least) faster than Emacs. But when it comes down to it, it's what you work best with that matters. If you're most productive in Eclipse, more power to you. Same if you ...


40

I had some thoughts on online editors, but my internet connection is down so I can't remember them.


33

These are my favorite features of my favorite IDE, IntelliJ, which I like using for Java, PHP, Javascript, HTML, even ActionScript. Error checking - Like live spell check for code. Absolutely essential. Code navigation - Ctrl+click on a function, variable, type to go to the definition. (IntelliJ is very good at this in all of the above languages) Code ...


30

The idea of being dependent on an IDE to understand code at such a basic level seems anathema. It is not a question of understanding your code: given sufficient time, you can always locate the right variable with a basic text editor or even in a printout. As far as understanding the code goes, the IDE dependency absolutely does not exist. Locating your ...


23

Many (most?) of the best programmers I know despise IDEs and rely solely on Emacs. I am not quite so diehard, and use both Eclipse and Emacs, but there are a couple of reasons I prefer using Emacs: Consistent experience with ANY language - Support in Eclipse for some of the newer languages (Scala, Clojure, etc.) is inconsistent at best, and subpar at ...


23

I'd suggest Notepad++. easy to use (integration into Explorer context menu) highly flexible, lots of addons available open source (free as in both "free speech" and "free beer")


22

Vim is a really good tool once you familiarize yourself with it. It starts up faster than any IDE or text editor I've used, and it has syntax highlighting and it indents the code correctly in most cases. It also helps you focus on the coding process itself, you won't be using the mouse at all to deal with it, that'll save you a lot of time when you're just ...


21

This is a changing space, every tool has its place in a professional's toolbox, it takes a true professional to know when each tool is appropriate to use. That said, not all tools are made the same, Dreamweaver was cutting edge a decade ago, there are better tools today. Tools like Flux and even Coda are invaluable for rapidly developing high quality code ...


21

Visual Studio is so convenient that after working with it for a while it is difficult to use a different IDE. It has a lot of handy tools and a bunch of plugins available, so practically it has every feature you would need. On the other hand, whatever language you learn, it is recommended to use command line at the beginning, so you can better understand ...


19

Refactoring facilities (Renaming affects dependencies/Extract Method/Extract interface etc.) Intellisense (or any other code completion functionality) Error checking (the IDE actually knows its symbols) No setup hassle Integrated compiler Integrated debugger Better navigation to and from references/declarations Project templates / file templates GUI ...


18

shouldn't we drop them and trying to invent or looking for something new? The full answer: A UNIX wizard hears cries of torment from his apprentice's computer room where the apprentice is studying, and goes to investigate. He finds the apprentice in obvious distress, nearly on the verge of tears. "What's the problem?" he asks. ...


15

Learn elisp. It allows you to program any shortcut you can think of. Any time you find yourself performing a multi-step process for something useful, you make a function out of it and bind it to a hotkey combo. It lets you experiment with functional programming - learning a new paradigm is a good way to expand your horizons.


15

LaTeX is what you need. MiKTeX - for Windows. Text Editors Kile - for Linux. TeXnicCenter for Windows. Documentation Free LaTeX documentation. Complexity comparison


15

Importance of vi is that you will always find it on any flavor of UNIX (standard both in SysV and BSD flavors) or UNIX-like system. Note however it might be original vi, not vim. You're not guaranteed to have any other editor installed. Also in Linux it's in /bin, so it's available even if /usr failed to mount.


15

Essentially it comes down to the fact that you can do whatever you want without ever leaving the keyboard. There are lots of key bindings that let you do lots of things. There is a steep learning curve for those used to graphical (mouse) editors as it is a very different way of doing things. However, once you get familiar with it, you can move around and ...


15

I'm 22 (I'm guessing this meets your definition of new generation) and I use Vim (admittedly not Emacs) when I'm working with languages that don't have a first class IDE (examples of languages that do would be C#, Java, and Scala IMHO). I tend to find that the shortcuts available are more powerful and increase my productivity compared to an editor like gEdit ...


14

Vim starts faster than just about anything (anything sophisticated enough to have syntax highlighting anyway) and ships with C# syntax highlighting. As you're probably already aware though, the learning curve is steep. www.vim.org


13

10 X more productive? Not likely. I tend to think the multiplicative factors are more like 1.1, which does add up after a while. What Steve Yegge is talking about is really a reflection on being an expert in Emacs, and those are very rare. People who are achieving this multiplicative effect are actively customizing their Emacs experience by writing elisp ...


13

I’m 23. I’ve used Vim (yes, not Emacs, but still breaking a lance here for both) for 6 months now — 3 of them 8 hours a day at my job (JS/HTML/CSS). Everyone holds their breath in awe when I change 20 lines of code in three seconds. Or when I scroll through files one page per half a second and still keep the context. Or when I get NerdTree and a 3x2 window ...


12

[To the IDE] You had me at intellisense/autocomplete


12

I've been using emacs for the last 10 years (from and to), and I can only say that you are absolutely right. Back in the days, I used gnus and the w3 browser, but clearly they are no longer up to it when compared to dedicated programs. But, obviously, you cannot run Chrome in text mode so this is where emacs wins. And even there, I'd rather use lynx/elinks ...


12

I think the IDE's (Visual Studio, Eclipse, IntelliJ) are fit to solve another class of problems than the ones you solve with emacs / Vim. When you have a large platform to code on, with lots of libraries and high integration between all elements (sounds like Microsoft), an IDE will prove it's worth. Some will refer to this as "sticking libraries together" ...


11

Productivity. Is there any other justification that makes sense? For me, a well-designed IDE that centralizes a lot of the functions that I perform while programming -- creating and editing code, using source control, debugging, interacting with project management tools, communicating with other programmers, creating documentation, running automated tests -- ...



Only top voted, non community-wiki answers of a minimum length are eligible