Afghanistan is the ghetto of the world. We've sealed up the escape routes and may be about to send in the death squads.
I think the troop movements are all posturing. However the cruise missle attack on Afghanistan under Clinton shows just how narrow minded the government can be. 100 million spent on cruise missles would have bought a lot of sympathy instead.
IDEs build upon the CLI. Its not correct to compare an IDE to a CLI since they do different things. The IDE takes the place of the above things and ads functionality, so you can't correctly say its more advanced. That said IDEs allow much more productivity and ease of use. If you train yourself to navigate the fileystem quickly by memorizing your source tree, then you can gain some of the usefulness of an IDE, but lets face it. In a project with several thousand source files being modified by a dozen people, this isn't going to cut it. A colleague might have added a new directory structure that you can't effectively navigate.
In addition, IDEs provide language specific advantages. Visual Basic does syntax checking while you're editing. Visual C++ does autocomplete and has an oft overlooked feature called WizardBar. I hit control-n and it adds a new function to my object in both the.h(pp) and.cpp files. Then theres the tooltips that show me what the return type is and arguments for a function.
No one can argue that ides add significant functionality to the programming environment. The question of CLI vs IDE is moot since they don't provide the same functionality. One compliments the other. A better question would be: editor+CLI+makefile vs IDE. In that case I would say that IDEs will always provide more features with less pain.
Unless you program with edlin or debug or something similar then you're not doing true command line development.
Slashdot Mirror
Afghanistan is the ghetto of the world. We've sealed up the escape routes and may be about to send in the death squads.
I think the troop movements are all posturing. However the cruise missle attack on Afghanistan under Clinton shows just how narrow minded the government can be. 100 million spent on cruise missles would have bought a lot of sympathy instead.
haxor: I don't use a gui for my programming all I use is emacs, a file manager, and a makefile.
.h(pp) and .cpp files. Then theres the tooltips that show me what the return type is and arguments for a function.
emacs = macros + syntax highlighting + editing
file manager = workspace view
makefile = workspace file
IDEs build upon the CLI. Its not correct to compare an IDE to a CLI since they do different things. The IDE takes the place of the above things and ads functionality, so you can't correctly say its more advanced. That said IDEs allow much more productivity and ease of use. If you train yourself to navigate the fileystem quickly by memorizing your source tree, then you can gain some of the usefulness of an IDE, but lets face it. In a project with several thousand source files being modified by a dozen people, this isn't going to cut it. A colleague might have added a new directory structure that you can't effectively navigate.
In addition, IDEs provide language specific advantages. Visual Basic does syntax checking while you're editing. Visual C++ does autocomplete and has an oft overlooked feature called WizardBar. I hit control-n and it adds a new function to my object in both the
No one can argue that ides add significant functionality to the programming environment. The question of CLI vs IDE is moot since they don't provide the same functionality. One compliments the other. A better question would be: editor+CLI+makefile vs IDE. In that case I would say that IDEs will always provide more features with less pain.
Unless you program with edlin or debug or something similar then you're not doing true command line development.
Because CSS already stands for cascading style sheets and also content scrambling system, Why not call it something non-confusing like DivX.