Am 14.10.2014 um 22:08 schrieb "Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?=
<ola.fosheim.grostad+dl...@gmail.com>":
On Tuesday, 14 October 2014 at 19:49:08 UTC, Paulo Pinto wrote:
Am 14.10.2014 um 17:30 schrieb eles:
On Tuesday, 14 October 2014 at 14:56:53 UTC, eles wrote:
On Tuesday, 14 October 2014 at 13:52:24 UTC, eles wrote:
http://ask-beta.slashdot.org/story/14/04/30/1344224/c-and-the-stl-12-years-later-what-do-you-think-now
"I've been using it professionally for 15 years now, and if I observe
anything, it's that the longer I use it, the more my stuff looks like C.
I keep shaking my head at younger colleagues mis-using templates all
over the place ("re-usability!", and hour-long compile times, coupled
with really non-obvious implicit conversions and instantiations, never
mind the error messages), and object-oriented hierarchies where each
object is such a tiny part of the system that you need to remember 10
classes at the same time just to have a slight inkling of what this
thing is actually supposed to do."
Actually I prefer,
"I used to love c++ and berade people who used wimp languages like
Java. These days I mainly use java, and when I do have to use c++, it
feels painfully dated.
At to C++11, while it added some useful stuff, in general it feels
like it's just flailing while trying to bring in some of the language
features of newer/more modern languages. The new concurrency stuff in
particular is just plain unseemly.
Isn't concurrency/parallell stuff coming in C++17?
I can use other languages *today* or wait until 2020 for C++17 to be
available across all major compilers.
This assuming that they don't repeat the errors of C++11 in that regard.
I found the cppcon roundtable on concurrency interesting:
http://www.youtube.com/watch?v=AfI_0GzLWQ8
I did watch it, had no idea of the current problems with async.
--
Paulo
