4 ms·

The Chromium developers disregard Visual Studio and don't use Makefile but still manage somehow to write an incredibly high-quality code. How come? I think the

The Chromium developers disregard Visual Studio and don't use Makefile but still manage somehow to write an incredibly high-quality code. How come? I think the answer is because high-quality code doesn't come from Visual Studio and/or makefiles.

yeukhon 13y ago
Now you have just made an enemy of roughly half of the C/C++ developers in this world lol
- taspeotis 13y ago
  Why? It doesn't matter what IDE you use. It doesn't write the code for you.
- Danieru 13y ago
  Except everyone everywhere hates their build system. No one is making enemies here. No project thinks their code quality is a result of choosing make, or automake, or cmake, or qmake, or scons, or ant, or premake, or now I hear someone went and wrote a new one: GYP. Because of course if there is one thing the world needs, it's Yet Another Build System. Which as it happens, is also a build system: http://www.op59.net/yabs/readme.html http://www.op59.net/yabs/readme.html
  - raverbashing 13y ago
    I have a personal corollary that I am now extending. Two things always suck: bug tracking and build systems. What I think happens is that even if the foundations are different (and better), the ideas on how to do it are still the same as the first build systems. And that's the problem Overcomplicated, unhelpful, trying to fix language problems. Yes Makefiles are bad but a handcrafted one (or minimally automated) is usually much cleaner than most of the automated stuff.
- deathanatos 13y ago
  How? Visual Studio isn't available for my OS, and Makefiles just don't cut it anymore. (I typically use CMake, but I'll use anything that gives me fast build times and gets out of the way. Make typically isn't that.)¹ 1. I can do a build in one command. 2. It doesn't take forever. 3. It's easy to set up & modify. ¹Although, CMake generates makefiles. Does that count?

yeukhon 13y ago

Now you have just made an enemy of roughly half of the C/C++ developers in this world lol

taspeotis 13y ago
Why? It doesn't matter what IDE you use. It doesn't write the code for you.
Danieru 13y ago
Except everyone everywhere hates their build system. No one is making enemies here. No project thinks their code quality is a result of choosing make, or automake, or cmake, or qmake, or scons, or ant, or premake, or now I hear someone went and wrote a new one: GYP. Because of course if there is one thing the world needs, it's Yet Another Build System. Which as it happens, is also a build system: http://www.op59.net/yabs/readme.html http://www.op59.net/yabs/readme.html
- raverbashing 13y ago
  I have a personal corollary that I am now extending. Two things always suck: bug tracking and build systems. What I think happens is that even if the foundations are different (and better), the ideas on how to do it are still the same as the first build systems. And that's the problem Overcomplicated, unhelpful, trying to fix language problems. Yes Makefiles are bad but a handcrafted one (or minimally automated) is usually much cleaner than most of the automated stuff.
deathanatos 13y ago
How? Visual Studio isn't available for my OS, and Makefiles just don't cut it anymore. (I typically use CMake, but I'll use anything that gives me fast build times and gets out of the way. Make typically isn't that.)¹ 1. I can do a build in one command. 2. It doesn't take forever. 3. It's easy to set up & modify. ¹Although, CMake generates makefiles. Does that count?