A Perspective on C++ Standardization in 2018

Re:A Perspective on C++ Standardization in 2018 by otabdeveloper1 on Saturday December 29, 2018 @05:56AM (#18783058)

  > Use C++98
  > Complain it's too simple to be expressive.
  > Get C++17
  > Complain it's too expressive to be simple.

Sometimes I think the real goal behind these complaints is not learning anything new or programming anything interesting.

[ Parent | on HN ]

Re:A Perspective on C++ Standardization in 2018 by mschuetz on Saturday December 29, 2018 @07:43AM (#18783338)

Oh I absolutely love C++11, 14 and 17. It's just that there are always some really dumb parts that are shipped together with the good parts. Like mandatory begin and end iterators for list comprehension, iota, unreadable syntax of C++20 ranges, etc.

[ Parent | on HN ]

Re:A Perspective on C++ Standardization in 2018 by minipci1321 on Saturday December 29, 2018 @06:41AM (#18783194)

Well, one objective part I can see in these complaints, is that it seems to be hard to assemble a sufficiently big team of sufficiently qualified C++ developers, for what the project requires. C++ skills are scarce and expensive. This seems to be confirmed by my own experience in my waters.

And then people proceed to put all blame on the language alone, and this does not match the reality anymore. Again, in my waters.

[ Parent | on HN ]