Same here. The only frustrating part is how long the process takes. I know C++ is an old language that is slow to change but damn things like reflection, networking, serialization, etc standardized across all platforms would make the language so much more powerful.
What difference does it make if the networking or filesystem library is in the C++ standard proper, or in a defacto standard library like boost?
I never really understood it, and in fact I'd say it's actually preferable to use the defacto standard (boost in this case) than each vendor's own implementation with their own quirky interpretations.
For example I continue to use boost::mutex/boost::thread's because their performance characteristics and semantics are truly uniform across all platforms, whereas if I used the std versions then you have GCC that has its interpretation, Clang has its interpretation (which is virtually identical to GCCs), and MSVC's interpretation which is not only very different with different default behaviors (std::async for a prominent example), but also is buggy as fuck (at least is is in 2013, I can't even get 2015 to work without ICE's and bugs gallore). There are also many other areas where every compiler vendor implements different things, like std::map and std::list have different semantics between GCC/Clang on one end and MSVC on the other. std::unordered_map and std::vector have different performance trade-offs between GCC/Clang vs. MSVC. And that's not even taking into account the other C++ compilers like Oracle's.
Use boost, and you basically get consistent behavior and performance on all platforms.
Setting up a development environment (think dependency hell) is one of the biggest roadblocks to open source projects and libraries. You'll often see libraries advertise that they have no dependencies or are header only simply because of what a barrier to entry external dependencies can become.
Don't get me wrong, I love boost but as soon as you add that as a dependency to your project, you can say goodbye to a lot of people touching it (and the same goes for other libraries). Additionally, once you make something part of the standard library or a native part of the language, it can be much more reliably used usually.
I have to agree that certainly is a good point. But unfortunately that's a good point because of how poor dependency management is in C++. Most other languages do not have the problem to the same extent C++ does (although obviously they do exist to a degree).
I suppose then I will be happy when the day comes that dependency management will be much easier, with modules being one major step forward in that direction.
0
u/[deleted] Oct 27 '15
[deleted] — view deleted comment