Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

21st Century C++

cacm.acm.org

Post reply on HN
Print view View original

131–140 of 281 posts

Re: 21st Century C++

#131

Post by imron »

midnightclubbed wrote: post #106
imron wrote: post #94

I want to love C++. Over my career I’ve written hundreds of thousands of lines of it. But keeping up with it is time consuming and more and more I find myself reaching for other languages.

You don't 'have' to keep up with the language and I don't know that many people try to keep up with every single new feature - but it is worse to be one of those programmers for whom C++ stopped at C++03 and fight any feature introduced since then (the same people generally have strong opinions about templates too). There are certainly better tools for many jobs and it is important to have languages to reach for depe…

I’ve been using c++ since the late 90’s but am not stuck there.

I was using c++11 when it was still called c++0x (and even before that when many of the features were developing in boost).

I took a break for a few years over c++14, but caught up again for c++17 and parts of c++20...

Which puts me 5-6 years behind the current state of things and there’s even more new features (and complexity) on the horizon.

I’m supportive of efforts to improve and modernize c++, but it feels like change didn’t happen at all for far too long and now change is happening too fast.

The ‘design by committee’ with everyone wanting their pet feature plus the kitchen sink thrown in doesn’t help reduce complexity.

Neither does implementing half-baked features from other ‘currently trendy’ languages.

It’s an enormous amount of complexity - and maybe for most code there’s not that much extra actual complexity involved but it feels overwhelming.

Re: 21st Century C++

#132

Post by mempko »

That's why C++ is still around today, it was built on some solid principles. Bjarne is such a good language designer because he never abandoned it. Lesser designers make a language and start another in 5 or 10 years. Bjarne saw the value in what he created and had a sense of responsibility to those using it to keep making it better and take their projects seriously.

Whenever I have an idea and I start a project, I start with C++ because I know if the idea works out, the project can grow and work 10 years later.

Re: 21st Century C++

#133

Post by galkk »

musicale wrote: post #121
midnightclubbed wrote: post #111

Earlier quoted context omitted.

I have used auto liberally for 8+ years; maybe I'm accustomed to reading code containing it but I really can't think of it being a problem. I feel like auto increases readability, the only thing I dislike is that they didnt make it a reference by default. Where do you see difficult to track down performance/memory implications? Lambda comes to mind and maybe coroutines (yet to use them but guessing there may be some…

I just wish they hadn't repurposed the old "auto" keyword from C and had used a new keyword like "var" or "let". #define var auto #define let auto

If we're going that route, how about

   #define var auto
   #define let const auto

?

Re: 21st Century C++

#134

Post by layer8 »

imron wrote: post #131
midnightclubbed wrote: post #106

Earlier quoted context omitted.

You don't 'have' to keep up with the language and I don't know that many people try to keep up with every single new feature - but it is worse to be one of those programmers for whom C++ stopped at C++03 and fight any feature introduced since then (the same people generally have strong opinions about templates too). There are certainly better tools for many jobs and it is important to have languages to reach for depe…

I’ve been using c++ since the late 90’s but am not stuck there. I was using c++11 when it was still called c++0x (and even before that when many of the features were developing in boost). I took a break for a few years over c++14, but caught up again for c++17 and parts of c++20... Which puts me 5-6 years behind the current state of things and there’s even more new features (and complexity) on the horizon. I’m suppor…

It’s okay to be a few years behind the standard, the compilers tend to be as well.

Re: 21st Century C++

#135

Post by justanotheratom »

mempko wrote: post #129
justanotheratom wrote: post #127

C++ should be known for the amount of collective brain cycles wasted on arguing what subset of C++ is the right one to use.

Professionals know what tool to use for a job. Does it take time to become good? Of course, like anything.

Not a question of difficulty or skill. I am saying professionals can't agree what subset to use!

Re: 21st Century C++

#137

Post by bogeholm »

codr7 wrote: post #97
imron wrote: post #94

I want to love C++. Over my career I’ve written hundreds of thousands of lines of it. But keeping up with it is time consuming and more and more I find myself reaching for other languages.

I've been writing C++ since 1996-ish. Less and less, for sure. Nothing the past few years. They killed it.

Almost a haiku :)

Re: 21st Century C++

#139

Post by sixthDot »

mempko wrote: post #79

Bjarne Stroustrup (the creator of C++) is the best language designer. Many language designers will create a language, work on it for a couple years, and then go and make another language. Stroustrup on the other hand has been methodically working on C++ and each year the language becomes better.

So now even H news are being poluted with IA.

Re: 21st Century C++

#140

Post by imron »

pro14 wrote: post #124

is the job market for C++ developers still good?

Depends. For certain fields the pay is great and there’s a dearth of candidates.

For other fields there is also a dearth of candidates but the pay falls short and you’ll be leaving tens of thousands of dollars on the table compared to what you could get with other languages.

Post reply on HN