4 ms·

Looks very nice. C++ is seriously behind in terms of tooling so any project in this space is most welcome. Of course we are entering the xkcd 927 stage now and

Looks very nice. C++ is seriously behind in terms of tooling so any project in this space is most welcome. Of course we are entering the xkcd 927 stage now and the only thing even remotely close to being a defacto standard is CMake. What we really need is the committee to start aggressively prioritizing on useful stuff like tooling, build system, modules, packages and bug fixes - and less on esoteric language features that just make the language more complex.

rewrking 4y ago
Couldn't agree more! Glad there are others that feel this way.
synergy20 4y ago
true, c++ renews itself every 3 years which is great, except that its tooling remains the same. equip c++ with new tooling like what golang and rust have will be a huge boost to this language.
- dasloop 4y ago
  With the exception of CMake evolution (now days a defacto standard), package managers (as Conan or vcpkg) or the support for new C++ standards in major compilers (clang, gcc, Visual) ;)
  - TillE 4y ago
    It's good that the C++ world has effectively standardized on something, but CMake still has a steep learning curve. I hate its structure as a jumbled mess of independent commands. It needs more guidance for making simple, typical projects easy to set up, at the very least more stuff that works like ExternalProject_Add (a big powerful command with all its options clearly documented on one page).
    - MafellUser 4y ago
      OTOH learning how to debug cmake will guarantee your employment for life so there's an incentive.
    - dasloop 4y ago
      ExternalProject_Add -> vcpkg or Conan. I have more experience with vcpkg and the steps are: 1) declare your dependencies in a vcpkg.json file (similar to npm's package.json). Example: { ... "dependencies": [ "openssl" ] } 2) Add it to your CMakeLists.txt file. Example: find_package(OpenSSL REQUIRED) target_link_libraries(main PRIVATE OpenSSL::SSL OpenSSL::Crypto)

rewrking 4y ago

Couldn't agree more! Glad there are others that feel this way.

synergy20 4y ago

true, c++ renews itself every 3 years which is great, except that its tooling remains the same. equip c++ with new tooling like what golang and rust have will be a huge boost to this language.

dasloop 4y ago
With the exception of CMake evolution (now days a defacto standard), package managers (as Conan or vcpkg) or the support for new C++ standards in major compilers (clang, gcc, Visual) ;)
- TillE 4y ago
  It's good that the C++ world has effectively standardized on something, but CMake still has a steep learning curve. I hate its structure as a jumbled mess of independent commands. It needs more guidance for making simple, typical projects easy to set up, at the very least more stuff that works like ExternalProject_Add (a big powerful command with all its options clearly documented on one page).
  - MafellUser 4y ago
    OTOH learning how to debug cmake will guarantee your employment for life so there's an incentive.
  - dasloop 4y ago
    ExternalProject_Add -> vcpkg or Conan. I have more experience with vcpkg and the steps are: 1) declare your dependencies in a vcpkg.json file (similar to npm's package.json). Example: { ... "dependencies": [ "openssl" ] } 2) Add it to your CMakeLists.txt file. Example: find_package(OpenSSL REQUIRED) target_link_libraries(main PRIVATE OpenSSL::SSL OpenSSL::Crypto)