Imagine a giant cock flying towards your mouth, and there's nothing you can do about it. And you're like "Oh man, I'm gonna have to suck this thing", and you brace yourself to suck this giant cock. But then, at the last moment, it changes trajectory and hits you in the eye. You think to yourself "Well, at least I got that out of the way", but then the giant cock rears back and stabs your eye again, and again, and again. Eventually, this giant cock is penetrating your gray matter, and you begin to lose control over your motor skills. That's when the giant cock slaps you across the cheek, causing you to fall out of your chair. Unable to move and at your most vulnerable, the giant cock finally lodges itself in your anus, where it rests uncomfortable for 4, maybe 5 hours. That's what using and IDE is like.
IDEs have a lot to offer over just a text editor. I think all programmers should be competent enough to do everything with just a text editor, but IDEs certainly ease the burden of many tasks.
Pre-compilation compilation units enable IDEs to detect errors in syntax and structure before the oblivious programmer would find them in the sometimes cryptic output of the compiler. Refactoring tools allow programmers to quickly and easily refactor objects which is a lot easier than using `find and replace in selection' because the refactoring tools are context specific. The IDE can also give programmers complete outlines of their programs. And the IDE enables the programmer to quickly deploy different compiler settings and debuggers with easy-to-set break points.
Those are some of the reasons why I like IDEs. I think that in most cases they are more efficient productivity-wise. In other cases IDEs are just extraneous.
Name:
Anonymous2011-06-25 16:08
>>9
Also, on that note, at what point are text editors text editors and IDEs IDEs? Many `advanced' text editors have many features of an IDE. Likewise, most IDEs can be used as text editors.
Name:
Anonymous2011-06-25 17:22
OP has mastered the art of looking intelligent to idiots while at the same time looking like a complete fucking moron to real hackers. Good job OP.
People use vi because they like the features of vi and don't need or want the features of other IDEs. Pretending that Visual Studio doesn't have benefits over vi--despite whether or not those benefits outweigh the limitations--doesn't not make you look like you know what you're talking about.
>>13 Pretending that Visual Studio doesn't have benefits over vi
vi doesn't have many features. I don't really know what VS has over vim (once configured), unless you consider ``modeless'' a feature.
Name:
Anonymous2011-06-27 5:25
IDEs are nice.
Text editors optimize the wrong thing. entering the code is by far not the bottleneck. It is better to help with debugging than to help with typing.
because using auto completion makes you a bad programmer? it makes it easier, programming is still done by the person using the IDE
of course GUI tools are horrible, but auto completion is pretty much the most useful tool ever
Name:
Anonymous2011-06-27 11:34
Geehrte Damen und Herren wären sie bereit für einen Augenblick die Augen zu schließen und sich vorzustellen wie ich langsam meinen Penis in ihren Mund führe, halten sie kurz inne, riechen sie diesen Würzigen strengen Duft ein ungewaschenen Glieds? Nähmen sie sich zeit und lassen sie es auf sich wirken während ich langsam weiter ihren Rachen runter gleite merken sie die plötzlich Luftknappheit? Erschrecken sie sich nicht sie werden sich schnell dran gewöhnen weinen sie ruhig wen ihn danach zumute spüren sie dem Rhythmus des pochenden Gliedes konzentrieren sie einzig und allein auf die würzige Zwiebelwurst die ihren brechreiz wieder und abermals auf die probe stellt. Und dann werden sie eins, eins mit dem Moment der Vollkommenen Entleerung genießen sie jeden einzigen klebrigen tropfen der ihr Kehle herunter tropft und werden sie sich dem Leben in seiner vollen Wonne bewusst.
Name:
Anonymous2011-06-27 11:58
When using an IDE I frequently feel like I have no idea what is going on in the compilation process. It works, but I'm not in complete control over what is going on. If I use vim + g++ it doesn't automatically include all the libraries or set the correct paths.
I also like having the programs shout at me when I make a mistake. When I forget a bracket and Sepples-sama gets all mad and spews a hundred errors at me, I feel like she is the only one who really cares about me.
Name:
Anonymous2011-06-27 12:21
Fixt version (i know u waited for that)
Geehrte Damen und Herren wären sie bereit für einen Augenblick die Augen zu schließen und sich vorzustellen wie ich langsam meinen Penis in ihren Mund führe, halten sie kurz inne, riechen sie diesen Würzigen strengen Duft eines ungewaschenen Glieds? Nähmen sie sich zeit und lassen sie es auf sich wirken während ich langsam weiter ihren Rachen runter gleite merken sie die plötzlich Luftknappheit? Erschrecken sie sich nicht sie werden sich schnell dran gewöhnen weinen sie ruhig wen ihn danach zumute ist spüren sie dem Rhythmus des pochenden Gliedes konzentrieren sie sich einzig und allein auf die würzige Zwiebelwurst die ihren brechreiz wieder und abermals auf die probe stellt. Und dann werden sie eins, eins mit dem Moment der Vollkommenen Entleerung genießen sie jeden einzigen klebrigen tropfen der ihr Kehle herunter tropft und werden sie sich dem Leben in seiner vollen Wonne bewusst.
Name:
Anonymous2011-06-27 13:25
>>18
This is the right answer. I strongly dislike the amount of information that an IDE (like VS) hides from me, but it is worth the sacrifice to get the visibility that the debugger provides. You could probably piece together some custom tools and get something close to the streamlined-ness of VS, but why bother?
I will stick with VS until there's something different that provides this level of convenience:
1) Type some code.
2) Set a breakpoint at an line of source.
3) Press a key to compile/link/run it.
4) Code stops at set breakpoint.
5) Immediate visibility into all local variables, call stack, registers, memory contents, disassembly... plus single keystrokes for single stepping, "step over," "run to cursor," etc...
Yeah, all those functions are available in GDB or your favorite command-line debugger, but as >>18-san said, the bottleneck in development is the time consumed in doing exactly these things (unless you're writing toy code).