4 ms·

Without commenting on Node.native, I'd just like to note that C++11 isn't your grandparents' C++ anymore. An experienced programmer probably can write code in C

Without commenting on Node.native, I'd just like to note that C++11 isn't your grandparents' C++ anymore. An experienced programmer probably can write code in C++11 that is almost as elegant as, say, the equivalent C# code. And for larger projects many people would prefer something like C# to JavaScript, if only for the static typing.

baq 15y ago
the problem isn't writing code, the problem is build environment and deployment - correct versions of compilers, headers, libraries, makefiles, cmakelists, wafs, scons', bjams, whatevers...
- alexchamberlain 15y ago
  Is it really an issue? Are you proud of the fact that you can't sudo apt-get a few packages? I'm not a fan of moving away from Makefiles, however. Makefiles are sooo simple, why complicate it?
  - baq 15y ago
    sudo apt-get a few packages is great when it works, but if you want/need a newer boost version, you're on your own. Makefiles are tedious to write and maintain in anything but a toy application. That's not to say everything else isn't, but most of the time you can save yourself some hassle.
  - omaranto 15y ago
    I used to feel that way about Make until I tried Rake. I'll never go back now, I think build scripts feel the need for a general purpose language often enough that it really pays to have them as an embedded DSL in a scripting language.
  - pjmlp 15y ago
    Makefiles are only simple if you are only supporting a single operating system, and a few build configurations.
    - dpiers 15y ago
      I've worked on a makefile that built shaders, libs, and assorted executables for multiple projects across 6 platforms, and I can confirm this.
  - dkersten 15y ago
    Is it really an issue? No. Its not. I've been programming primarily in C++ for a few years (been using it as a hobbyist programmer since about 2002 and on and off professionally over the last 4 years) and this has never been an issue for me.
- _stephan 15y ago
  If you're developing company-internal stuff, you can just standardize on one compiler and/or statically link everything.
Animus7 15y ago
I've actually been using C++11 for two years now (experimental stuff in GCC), and yes I agree: C++ is loads better than it used to be, and it's a pleasure to work with. That still doesn't mean it's a good idea to write a full web app in a C++ event loop while doing your own memory management. I've tried this (in C++11 no less), and it took nearly 30K LOC for me to admit defeat. I wish I were joking.

baq 15y ago

the problem isn't writing code, the problem is build environment and deployment - correct versions of compilers, headers, libraries, makefiles, cmakelists, wafs, scons', bjams, whatevers...

alexchamberlain 15y ago
Is it really an issue? Are you proud of the fact that you can't sudo apt-get a few packages? I'm not a fan of moving away from Makefiles, however. Makefiles are sooo simple, why complicate it?
- baq 15y ago
  sudo apt-get a few packages is great when it works, but if you want/need a newer boost version, you're on your own. Makefiles are tedious to write and maintain in anything but a toy application. That's not to say everything else isn't, but most of the time you can save yourself some hassle.
- omaranto 15y ago
  I used to feel that way about Make until I tried Rake. I'll never go back now, I think build scripts feel the need for a general purpose language often enough that it really pays to have them as an embedded DSL in a scripting language.
- pjmlp 15y ago
  Makefiles are only simple if you are only supporting a single operating system, and a few build configurations.
  - dpiers 15y ago
    I've worked on a makefile that built shaders, libs, and assorted executables for multiple projects across 6 platforms, and I can confirm this.
- dkersten 15y ago
  Is it really an issue? No. Its not. I've been programming primarily in C++ for a few years (been using it as a hobbyist programmer since about 2002 and on and off professionally over the last 4 years) and this has never been an issue for me.
_stephan 15y ago
If you're developing company-internal stuff, you can just standardize on one compiler and/or statically link everything.

Animus7 15y ago

I've actually been using C++11 for two years now (experimental stuff in GCC), and yes I agree: C++ is loads better than it used to be, and it's a pleasure to work with. That still doesn't mean it's a good idea to write a full web app in a C++ event loop while doing your own memory management. I've tried this (in C++11 no less), and it took nearly 30K LOC for me to admit defeat. I wish I were joking.