>>330494It doesn't really work like that. "C" isn't just "C", there are lots of different incompatible dialects, and the platform you're targetting dictates your C dialect and toolchain (compiler, linker, standard library, debugger), which in turn dictates your IDE.
For example, if you're targetting windows, that means MSVCC, which in turn means Visual Studio. If you're targetting Linux, GCC dictates Eclipse. Mac, Apple LLVM, Xcode. And so on.
If you're not targetting a platform, and are just doing this to learn programming, for the love of god don't start with C: learn a high-level language like JavaScript or Python, then once you can program, learn a low-level language like C. Trying to learn procedural programming and manual memory management and static typing and unsafe pointers at the same time, when you could learn them one at a time, is going to be frustrating and ineffective.
In programming, you don't learn nearly as much from failure as you do from success; the two hours you spent trying to make a C program not segfault doesn't teach you anything compared to the minute in which you actually fix it. If you start with a higher-level language, you'll spend more time succeeding and learning, and less time flailing around not learning anything.
I reckon most people can learn Python then C in the time it takes to get from zero to writing C programs that manage memory and pointers correctly.
