5 ms·

GO style co-routines and native JSON support would pretty much consign GO to history, IMO.

• jerf 5y ago
  If things could be "consigned to history" by C++ adding more features, there'd hardly be any other languages left! It has all the features. That's its biggest problem.
  • logicchains 5y ago
    Noo, it's missing something basic: struct introspection. Unlike almost every other modern language, it's not possible to write a generic "ToJson" or "ToString" that will work for any struct.
    • quietbritishjim 5y ago
      Not sure whether that's a sarcastic commentary or your just not aware, but C++ will, of course, also get (static) reflection https://en.cppreference.com/w/cpp/keyword/reflexpr https://en.cppreference.com/w/cpp/keyword/reflexpr
  • pjmlp 5y ago
    Usually only C++ gets the blame, but that is only because most don't pay attention to other language's reference manuals and standard libraries. I love to pick on Python for such examples, because it is considered to be the new BASIC, yet when I pick the standard language reference + standard library, the amount of pages outgrows those of ISO C++. Then there is the list of breaking changes that have happened even across minor versions since Python 1.0.
• hedora 5y ago
  JSON for modern C++ and this article pretty much cover it. C++ tends to be the second best language for everything, and this is no exception. Go beats it at Go’s own niche: it has great compilation times and it forces you down a sane asynchronous programming path. C++ fails on both those criteria. However, once you fall off the happy path in Go, you’re probably completely screwed, where as with C++, you’re already using the second best language for whatever your new problem is.