News for hackers. Stuff that matters.
Re:C++ the Good Parts (2014) by secondcoming on Thursday October 01, 2020 @08:04AM (#24649926)
Well that's not C++'s fault. Those people are either stuck on a particular compiler version, are in a maintenance mode, or are just unwilling to improve themselves. Maybe there's job security in being able to write code in a deprecated style.
Re:C++ the Good Parts (2014) by badsectoracula on Thursday October 01, 2020 @01:29PM (#24653744)
> or are just unwilling to improve themselves

Or they may not see that stuff as an improvement in the first place (e.g. see Orthodox C++[0]).

[0] https://gist.github.com/bkaradzic/2e39896bc7d8c34e042b

Re:C++ the Good Parts (2014) by Jtsummers on Thursday October 01, 2020 @03:45PM (#24655403)
If I'm reading that right, they start off talking about a minimalist/reduced subset of C++, and then end up concluding: Use C++14 (now two standards ago) and we'll probably recommend C++17 in 2022 (5 year delay).

That seems like a rather weak conclusion given all the words that preceded it. You might as well just start and end with this:

New standards have issues, people don't know how to use them correctly, and compilers are slow to catch up. Wait 5 years to use a standard so all these things are worked out, and you don't have to worry about the details that don't stick.

Re:C++ the Good Parts (2014) by badsectoracula on Friday October 02, 2020 @07:35AM (#24661534)
The C++14 part seem to be added lately and indeed sounds contradictory to what was written previously. As a comment below writes though they use the original Orthodox C++ idea without the C++14 part (and TBH i think the whole "committee" part is a tongue-in-cheek joke).

In any case this is just an example, there are a couple of similar "subsets" with the same idea of keeping C++ use to its bare minimum, it is just that i remember this one because of the name :-P

Re:C++ the Good Parts (2014) by hyperpl on Thursday October 01, 2020 @03:18PM (#24655111)
Wow, I thought I was alone.
Re:C++ the Good Parts (2014) by ncmncm on Friday October 02, 2020 @05:53PM (#24667396)
It is always the right time to learn modern C++.

Discomfort is not a valid reason to avoid learning new things.

Re:C++ the Good Parts (2014) by unishark on Thursday October 01, 2020 @08:47AM (#24650237)
Historically there was a big performance hit for using the fancy added abstractions of C++. Don't know if it's still that bad. But in the past it cost a factor of two or so, whenever I tried to get fancy.
Re:C++ the Good Parts (2014) by jcelerier on Thursday October 01, 2020 @11:01AM (#24651649)
> Historically there was a big performance hit for using the fancy added abstractions of C++. Don't know if it's still that bad. But in the past it cost a factor of two or so, whenever I tried to get fancy.

I don't know how much back in the past it is, but pretty much every time in the last ten years I tried to beat a C++ abstraction, I almost never managed to substantially improve (and since gcc.godbolt.org exists it made it much easier to witness that most of the abstraction layers entirely disappear at -O2)

Re:C++ the Good Parts (2014) by ncmncm on Friday October 02, 2020 @08:33PM (#24668443)
Historically, meaning "in the '90s". It has been quite a long time since the '90s. Many readers here weren't even born yet when C++ abstraction overhead was last a thing.
Re:C++ the Good Parts (2014) by pjmlp on Thursday October 01, 2020 @08:27AM (#24650091)
Like Android NDK?
Re:C++ the Good Parts (2014) by secondcoming on Thursday October 01, 2020 @12:34PM (#24652974)
No idea, I've no experience with it.
Re:C++ the Good Parts (2014) by pjmlp on Friday October 02, 2020 @02:03AM (#24659405)
You should, then you will see how much C++ it actually uses.

It exposes everything as C APIs, even thought it is a mix of Java and C++ on the implementation side, leaving the C++ developers to write their own type safe abstractions from scratch.

Most just can't be bothered and write C in C++.

Then there is the whole issue how, following Google C++'s guidelines, the NDK is actually implemented.