3 ms·
Lately I've been working with c++ and, at least in my experience, as a developer who's native tongue isn't c++, many of the answers have failed to keep up with
by cdoxsey 8y ago
Lately I've been working with c++ and, at least in my experience, as a developer who's native tongue isn't c++, many of the answers have failed to keep up with the radical changes in the language in the last 10 years. Post-17 C++ is completely different from pre-11 C++.
That said there's usually an answer further down the page with a more up to date solution, it's just not the accepted or most popular one.
- umvi 8y agoTrue, but consider your user base. I, for one, maintain legacy C/C++98 code. C++17 answers are not helpful to me because the legacy system does not have a new enough compiler, sysroot, etc for me to take advantage of them. It's not like web development where users' browsers auto-update and you can start immediately using the newest versions of everything. Only our newest projects are using modern C++ (14). I would wager the majority of C++ users "in the field" are using 11 and below and haven't had a good opportunity to switch to 14 or 17 yet. As such, answers that seem outdated to you may be a good fit for the majority. It's sort of like how any native answers automatically float higher than boost answers - why is this? Because most c++ users are not using boost and have no interest in using boost.