Score: IDE Coders 1 - Text Coders 0 Learning curveĪrgument: I would lose productivity learning to use a new tool.Ĭounterargument: At the beginning, yes, but you will definitely gain it back – and more – later. Let’s keep score: An IDE is too slowĪrgument: The IDE is too slow and uses up too much computer resources.Ĭounterargument: It’s cheaper to buy a good computer with enough resources than lose the extra productivity that an IDE can give you. But I do think some of the arguments to use them are not completely valid. “ With the same text editor that I use locally, I can work remotely when I connect to a server via SSH.”Įxtracting the data from my informal survey, I discovered that indeed most senior developers use text editors. “ Recently, I’m starting to see the value of using WebStorm and RubyMine, though I do still think they’re a little slow and consume quite a few resources on my computer.”
“ I feel that bash will never let me down.” “ I do think I can edit faster in VI than with a mouse-based backspacing editor.” I reached out to some developers to find out what they thought: Ok, I’ll confess: I really was out to prove those dinosaurs wrong (I know, I was being a little harsh on those zen programmers). I was on a mission to find the truth behind it all. Right? So could the real reason behind sticking to text editors be that more senior programmers are stuck in their ways and too stubborn to learn a new tool? Could it also be partly some form of snobbism where “real developers” would not be caught dead using a graphical user interface? But with IDEs, I can do everything I can on a text editor and so much more. If these super developers use text editors, could it be that it really is better to not use IDEs? Do I use them just because I don’t master all the shortcuts and tricks that let “real” programmers keep their hands on the keyboard? Perhaps. A regular “mere mortal” user would rely on the graphical user interface to navigate the computer to find files, rename files, create folders, but a “real” developer will open a terminal, type in commands and not rely on a graphical user interface at all! They know all about the command line, all the keyboard shortcuts – so they almost never need a mouse –, and they love adding and writing plugins to a plain text editor.
#Text editor vs ide software
It seems, however, that all the super experienced software developers never use IDEs. And I have access to templates, refactoring help, tools integration and much more, which really increases my productivity. I find and fix problems sooner because the IDE highlights syntax errors, unused variables, and suspicious code.
#Text editor vs ide code
I can program faster with the code completion or code insight features, which also helps me avoid typos.
Since I started programming, I’ve always used IDEs. The choice was either to become a real programmer and switch to a text editor, or to reinforce that I am a real programmer who uses an IDE! So I decided to dig a little deeper and collect opinions about this topic. I’ll start by making it clear that I belong to the first group and do care a little bit about the other group’s opinion. There are 10 types of programmers: those who use an IDE, and those who think that the ones who use an IDE are not real programmers. Catalina De la cuesta The IDE vs Text Editor Battle
0 kommentar(er)
