News for hackers. Stuff that matters.
Re:Multithreading in modern C++ by partycoder on Thursday April 28, 2016 @01:21PM (#11590466)
C++ was supposed to be portable. When you add a layer of threading, networking, etc. you are starting to commit to specifics of operating systems.

It's fine to keep this at a library level, and promote that library to be an standard on specific platforms. But C++ should not get tainted with OS specifics.

Re:Multithreading in modern C++ by pjmlp on Thursday April 28, 2016 @05:11PM (#11591911)
On the contrary having a big runtime is what makes a language portable by abstracting it from OS specific APIs.

I only care about OS specific code when using C or C++, not any other language with richer runtimes.

Actually, C's runtime is called UNIX and is packaged as POSIX for non-UNIX OSes.

Any C or C++ developer that wants "portable" code needs to litter their code with #ifdefs, for any dependency not on the standard library.

Re:Multithreading in modern C++ by exacube on Thursday April 28, 2016 @01:57PM (#11590701)
i'm pretty sure they're talking about adding these "layers" at the C++ stdlib level, not at the language level. So it will remain portable.