4 ms·

C brings in its own problems. Compiler (in)compatibilities, the need to install libraries on a machine to be able to compile and run programs. And besides, in C

by mjt0229 12y ago

C brings in its own problems. Compiler (in)compatibilities, the need to install libraries on a machine to be able to compile and run programs. And besides, in C you still have a build system problem - Make is fine, but it is definitely opinionated about how things happen, and you potentially have to write a lot more boilerplate to get a complex project built with Make than you do for Leiningen, Maven, SBT, etc.

Touche 12y ago
You don't have to use Make, there are a half a dozen other popular build systems.
- dkersten 12y ago
  I personally find that to be a horrible experience. Nothing worse than having to install a bunch of tools that you'll never use again, to compile someone else's project. For example, if you use CMake, tough, project A uses autotools. You use bjam? Project B uses QtCreator/QMake. You use Waf? Project C uses SCons. No thanks, just give me a standard build tool like leiningen and be done with it. (Ok, so its not "usually" that drastic, because there are only a handful of winners, but its happened a few times now that I've had to install Ruby - a language I don't use myself - just to run Rake to build some non-ruby software I've wanted...)
  - Touche 12y ago
    You're confusing the end user experience from the developer experience.
    - dkersten 12y ago
      I don't understand how. If I'm a developer, I've got the problem I mentioned. If I'm a user, I only have the problem if I build from source. Either way, with a standardised build tool like leiningen, I don't have the problem because, as a developer, I only need leiningen. As a user building from source, I only need leiningen. Both use cases are much simpler. However, having said that, I was only referring to the developer experience in my comment. I'm not really too sure what you read it as, but like I say above, I don't think it really matters: its a problem either way and both go away with a standard build tool.

by mjt0229 12y ago

Touche 12y ago

You don't have to use Make, there are a half a dozen other popular build systems.

dkersten 12y ago
I personally find that to be a horrible experience. Nothing worse than having to install a bunch of tools that you'll never use again, to compile someone else's project. For example, if you use CMake, tough, project A uses autotools. You use bjam? Project B uses QtCreator/QMake. You use Waf? Project C uses SCons. No thanks, just give me a standard build tool like leiningen and be done with it. (Ok, so its not "usually" that drastic, because there are only a handful of winners, but its happened a few times now that I've had to install Ruby - a language I don't use myself - just to run Rake to build some non-ruby software I've wanted...)
- Touche 12y ago
  You're confusing the end user experience from the developer experience.
  - dkersten 12y ago
    I don't understand how. If I'm a developer, I've got the problem I mentioned. If I'm a user, I only have the problem if I build from source. Either way, with a standardised build tool like leiningen, I don't have the problem because, as a developer, I only need leiningen. As a user building from source, I only need leiningen. Both use cases are much simpler. However, having said that, I was only referring to the developer experience in my comment. I'm not really too sure what you read it as, but like I say above, I don't think it really matters: its a problem either way and both go away with a standard build tool.