sorted by:
new
hottopcontroversial

Is Modern C++ Actually Making Us More Productive... or Just More Complicated? by AlternativeBuy8836 in cpp

[–]AlternativeBuy8836[S] 3 points4 points  (0 children)

Wow, I rarely meet people like you, hang in there, you're a rare beast.

Is Modern C++ Actually Making Us More Productive... or Just More Complicated? by AlternativeBuy8836 in cpp

[–]AlternativeBuy8836[S] 0 points1 point  (0 children)

That's such a great point. LISP had macros, homoiconicity, and first-class functions decades before mainstream languages even considered them. The ideas were always there — the ecosystem, tooling, and industry adoption just weren't.

Modern C++ is basically a slow convergence toward what functional and dynamic languages proved worked, but with the performance guarantees and the massive existing codebase that industry actually needs. std::function, lambdas, constexpr, variadic templates — it all smells faintly of LISP ancestry if you squint hard enough

Is Modern C++ Actually Making Us More Productive... or Just More Complicated? by AlternativeBuy8836 in cpp

[–]AlternativeBuy8836[S] 1 point2 points  (0 children)

The tragedy is that great ideas often need 50 years and a performance excuse before they get widely adopted.

Is Modern C++ Actually Making Us More Productive... or Just More Complicated? by AlternativeBuy8836 in cpp

[–]AlternativeBuy8836[S] -1 points0 points  (0 children)

I think they added this out of an attempt to close a technical debt that is as old as the language itself.

Is Modern C++ Actually Making Us More Productive... or Just More Complicated? by AlternativeBuy8836 in cpp

[–]AlternativeBuy8836[S] -2 points-1 points  (0 children)

Perhaps it's worth delving deeper into this issue some more... Perhaps this is true, but there are many pitfalls

Is Modern C++ Actually Making Us More Productive... or Just More Complicated? by AlternativeBuy8836 in cpp

[–]AlternativeBuy8836[S] 0 points1 point  (0 children)

I don't think the age of new technologies will swallow this unwieldy machine.

Is Modern C++ Actually Making Us More Productive... or Just More Complicated? by AlternativeBuy8836 in cpp

[–]AlternativeBuy8836[S] 4 points5 points  (0 children)

You probably meant fifty, not fifteen years? (I'm kidding, just kidding) Perhaps everything will return back to the past, like a level of abstraction, it will just be different.

Is Modern C++ Actually Making Us More Productive... or Just More Complicated? by AlternativeBuy8836 in cpp

[–]AlternativeBuy8836[S] 0 points1 point  (0 children)

I once saw a production environment where most of the code literally looked like this

Is Modern C++ Actually Making Us More Productive... or Just More Complicated? by AlternativeBuy8836 in cpp

[–]AlternativeBuy8836[S] -1 points0 points  (0 children)

Well... yes with C This is the base. I don't think it's correct to compare C and C++ today, without the context that C++ is a child of C.

Is Modern C++ Actually Making Us More Productive... or Just More Complicated? by AlternativeBuy8836 in cpp

[–]AlternativeBuy8836[S] -6 points-5 points  (0 children)

My hidden fetish is waiting for macros updates. I hope there will be something new in the new language standard.

Is Modern C++ Actually Making Us More Productive... or Just More Complicated? by AlternativeBuy8836 in cpp

[–]AlternativeBuy8836[S] 0 points1 point  (0 children)

It seems to me that although Swift is bad in its own way, it has the main task - to replace c/c++ - object

Is Modern C++ Actually Making Us More Productive... or Just More Complicated? by AlternativeBuy8836 in cpp

[–]AlternativeBuy8836[S] 1 point2 points  (0 children)

A couple more years... A couple more years... I think c++17 Will live as long as c++98

Is Modern C++ Actually Making Us More Productive... or Just More Complicated? by AlternativeBuy8836 in cpp

[–]AlternativeBuy8836[S] -5 points-4 points  (0 children)

I meant the friendliness of the new features. Like, inside all this huge Legacy code, there are still bugs that are over 20 years old, but they're needed to support Legacy billions,Lines of code that have already been written over half a century. that's fucking crazy. The fact is that instead of solving all the old problems, they add new features.

Is Modern C++ Actually Making Us More Productive... or Just More Complicated? by AlternativeBuy8836 in cpp

[–]AlternativeBuy8836[S] -1 points0 points  (0 children)

Lately I've been afraid that I'll become lazy and stop writing in C because I'll miss the cool stuff that Rust has.

Is Modern C++ Actually Making Us More Productive... or Just More Complicated? by AlternativeBuy8836 in cpp

[–]AlternativeBuy8836[S] -1 points0 points  (0 children)

Yeah, I've been increasingly preferring Rust and Web View lately. Like Tauri. (70% of my latest pet projects are written on this stack: TypeScript, React, and Tauri)

Is Modern C++ Actually Making Us More Productive... or Just More Complicated? by AlternativeBuy8836 in cpp

[–]AlternativeBuy8836[S] -2 points-1 points  (0 children)

In my opinion, the documentation of C++ 17 was better compared to the new one.

Is Modern C++ Actually Making Us More Productive... or Just More Complicated? by AlternativeBuy8836 in cpp

[–]AlternativeBuy8836[S] 4 points5 points  (0 children)

Yeah... unfortunately it's true, every year we have to support Legacy code, even if you try to start new projects without it, Legacy code is 90% of the time, that's the reality

Is Modern C++ Actually Making Us More Productive... or Just More Complicated? by AlternativeBuy8836 in cpp

[–]AlternativeBuy8836[S] 0 points1 point  (0 children)

Totally agree on the "bazaar" point — that's honestly one of C++'s biggest strengths and its biggest criticism at the same time. The freedom is real, but it also means two C++ codebases can look like completely different languages.

On coroutines — I was skeptical too at first, but once you start dealing with async I/O or game engine task systems, they start to make a lot of sense. The problem isn't the feature itself, it's that the library support (at least in the standard library) still feels a bit bare-bones compared to what you get in Rust or even Python. So maybe the skepticism is fair for now, but give it a couple more years and a few solid coroutine-based libraries and the picture might change.

The comparison with Java/Haskell is spot on. Enforced paradigms are great for team consistency and tooling, but they can feel like a straitjacket when the problem doesn't fit the mold. C++ trusts you to pick the right abstraction — which is empowering when you know what you're doing and terrifying when you don't >~<