|Are you telling me that I am supposed to know all of the short cuts and intricacies of whatever chosen IDE before I have even downloaded it?|
No. But you should understand the basic idea:
- Create a project
- Add files to that project
- Edit them
- Press the "build" button
These are very basic steps that anyone with any computer experience at all can figure out how to do in 5 minutes max.
How long do you think it would take someone to write a makefile if they've never done it before? Or how long to sort through a compiler's commandline options to figure out how to build a multi-file program?
I'm sure it would unconditionally take longer.
|A Shortcut is only useful if you know the shortcut in the first place, therefore useless to a beginner. You also still have to learn what the shortcut does anyway so what was the point?|
The "Build" option in all IDEs is a shortcut. I assumed that's the kind of thing you were talking about. It's actually a shortcut for a multi-step process... all steps of which must be done manually if not using an IDE (or in the case of a build script or makefile, you'd have to write the scripts to do these):
- Saves all files
- Compiles only files which have changed since last build
| A text file and a compiler can be up and running in a total of ten lines of text from the newbies point of view|
An IDE can be up and running in zero lines of text. Just click the "install" button and let it install. Then open it up.
In fact... most newbies don't even think of things in terms of "lines of text". Hell I don't even think of things like that and I've been using computers pretty much my whole life.
|this equates to about 5 minutes and it's usually laid out for them in a tutorial.|
I could make an easily comprehensible tutorial on how to get started with an IDE that is shorter than 5 minutes.
|Take your average hello world app, open up a terminal g++ helloworld.cpp|
- Open up IDE
- Press the "Build" button
I don't see how your approach is any simpler.
|You have compiled your first program and didn't even need to set up any include paths. (Which you have to do with many IDE's). |
I have never, ever had to set up any paths for anything in an IDE except for 3rd party lib installations. Ever. Not even when I was on Ubuntu.
You certainly don't have to do it for a "hello world" program.
|While the likelihood is very low, a corruption of a file is more likely with more files and there are multiple things that can go wrong. Many moving parts and all that. |
I will concede to this. However I still find it to be extremely unlikely and the odds of it happening to a beginner are low enough for it not to outweigh all the other benefits of using an IDE.
|Not one IDE has worked out of the box for me, so I gave up and returned to basics.|
If you're on Linux, I'm not surprised. Virtually nothing works out of the box on Linux in my experience.
|I agree with you that indepth discussion about Linking and Compiling so early on is somewhat of a higher level topic that can wait for a later date but I disagree that people shouldn't know at least a little about it.|
Knowledge about that has zero application until you start getting into multi-file programs (which absolute begginers are not going to do). And at that point I'd agree that people should learn the basic idea.
Anyway you haven't really addressed the bigger point, here.
If you are not using an IDE... how do you debug?