As far as the speed of ProjectBuilder, it has a lot to do.
When you start a project, of course, it has to build the file structure about the project which is fairly simple, depending on the type of project. You make changes to the files, add files, etc., and the project files are updated rather than your having to edit a makefile. When you create the programme, it does an exec* call to invoke the compiler and captures the output. It then puts the output back into a window, neatly cleaned up. When you run or debug, it runs the appropriate pieces and collects the input and output. This is part of the reason it doesn't always display stdout correctly. If you run a programme in debug mode, it will show it as it keeps track in a granular fashion.
I've been using IDEs since Borland's Turbo Pascal 3 in 1984 or 1985 alongside csh. IDEs are especially good for building visually-oriented applications, which tend to be complex in nature, with more than just one or two source files. I think you'll find that even Java programmers have left simple text editors alone since there's so much else to consider. Leave out a semicolon or a closing parenthesis and watch the error messages scroll past quickly.
It's hardly necessary to use a makefile anymore, regardless of the size of the project when a project manager can keep track of the project and let you concentrate on programming.
When you start a project, of course, it has to build the file structure about the project which is fairly simple, depending on the type of project. You make changes to the files, add files, etc., and the project files are updated rather than your having to edit a makefile. When you create the programme, it does an exec* call to invoke the compiler and captures the output. It then puts the output back into a window, neatly cleaned up. When you run or debug, it runs the appropriate pieces and collects the input and output. This is part of the reason it doesn't always display stdout correctly. If you run a programme in debug mode, it will show it as it keeps track in a granular fashion.
I've been using IDEs since Borland's Turbo Pascal 3 in 1984 or 1985 alongside csh. IDEs are especially good for building visually-oriented applications, which tend to be complex in nature, with more than just one or two source files. I think you'll find that even Java programmers have left simple text editors alone since there's so much else to consider. Leave out a semicolon or a closing parenthesis and watch the error messages scroll past quickly.
It's hardly necessary to use a makefile anymore, regardless of the size of the project when a project manager can keep track of the project and let you concentrate on programming.