News for hackers. Stuff that matters.
Re:In Defense of C++ by rramadass on Wednesday September 17, 2025 @12:43PM (#45278216)
Right on the money!

Other then hardcore embedded guys and/or folks dealing with legacy C code, I and most folks i know almost always use C++ in various forms i.e. "C++ as a better C", "Object-Oriented C++ with no template shenanigans", "Generic programming in C++ with templates and no OO", "Template metaprogramming magic", "use any subset of C++ from C++98 to C++23" etc. And of course you can mix-and-match all of the above as needed.

C++'s multi-paradigm support is so versatile that i don't know why folks on HN keep moaning about its complexity; it is the price you pay for the power you get. It is the only language that i can program in for itty-bitty MCUs all the way to large complicated distributed systems on multiple servers plus i can span all of applications to systems to bare-metal programming.

Re:In Defense of C++ by unscaled on Wednesday September 17, 2025 @11:32PM (#45284993)
In practice, C++ is a language family more than a single programming language. Every C++ project I've worked on essentially had its own idiolect of C++.
Re:In Defense of C++ by rramadass on Thursday September 18, 2025 @01:15AM (#45285702)
This is just a oft-repeated cliche and nothing more. Because C++ is a multi-paradigm language (with admittedly some less than ideal syntax/semantic choices) people overstate its complexity without much study/experience. Herd mentality than takes over and people start parroting and spreading the canard.

For the power and flexibility that C++ gives you, it is worth one's time to get familiar with and learn to use its complexity.

Re:In Defense of C++ by pod_krad on Sunday September 21, 2025 @07:03AM (#45321697)
>people overstate its complexity without much study/experience

The is no need in any experience to have ability to estimate C++ complexity. C++ specification is about 1500 pages.

Re:In Defense of C++ by rramadass on Monday September 22, 2025 @07:12AM (#45331814)
That is just silly; you don't need to read the entire specification to learn to use the language subsets productively as pointed out in my original comment here - https://news.ycombinator.com/item?id=45278216