DaemonR wrote:No header files, no messy makefiles or configuration scripts, fast compilation time, very easy to debug, very good ide's, and a very well structured standard library.
If you actually compile C# code with the command-line tools, you'll soon find yourself neck-deep in project files and configuration scripts. It's just that Visual Studio is a really good IDE and hides all that from you.
JackScott wrote:If you actually compile C# code with the command-line tools, you'll soon find yourself neck-deep in project files and configuration scripts. It's just that Visual Studio is a really good IDE and hides all that from you.
True. With really good alternative ide's like Monodevelop and Xamarin though, there's not really a reason to compile C# through the command line. Imho the best ide that I've ever used for C++ aside from Visual Studio is Qt; but it's not flexible enough to use for everything. The closest alternative to Qt is Eclipse, which has a good editor but is about as aesthetically pleasing as sloth from the goonies. Netbeans C++ is a ***** to configure with certain toolchains; I once got a bsod from it.
