> The issue is that C is not much of an "IDE language" This isn't an issue with the language so much as it is with the build systems, includes, library paths,

> The issue is that C is not much of an "IDE language" This isn't an issue with the language so much as it is with the build systems, includes, library paths, and tooling. Compare to Java (set the classpath to exactly the artifacts you want and IntelliJ uses its own build system unless you explicitly tell it otherwise), Python (set up a virtualenv with exactly what you want and PyCharm handles its own builds, insofar as Python builds). In C on Windows and Unix you have to figure out how to find and address includes and libraries in a cross platform way. CMake is probably the best bet. If they were in the position of, say, TurboC back in DOS days where they provided stdlib and you added everything else you wanted, they could do as good a job as for Java.