Thread 106906879

One thing is always true: where you can use C++, you can use C. In particular, if someone gave you C++ interfaces, a thin layer of wrappers will hide them. Using C instead of C++ has several practical benefits: faster development cycle, reduced complexity, better support by tools such as debuggers, higher portability and interoperability. When C++ is an option, C is probably a better option.

Another thing is always true: where you can use a managed environment (where the behavior of wrong programs is defined), using it will save a lot of trouble. C++ (like C) is designed for unmanaged environments (where the behavior of wrong programs is undefined). Unmanaged environments make it very hard to locate faults and impose no limit on the damage done by an undetected fault. In theory, C++ implementations can run in managed environments, but in practice they don't because of innumerable compatibility issues.

Yet another thing is almost always true: picking up a new language is easier for an experienced C++ programmer than working in C++. This is the result of the exceeding complexity of C++.

People who think there's no point in comparing programming languages, for example because "business considerations dominate technical considerations", are free to start their new projects in COBOL (COmmon Business-Oriented Language).

>>106906879 (OP)
>where you can use C++, you can use C.
in a small, well communicating team, with a homogenous level of proficiency.
c++ has the advantage of forcing the team into using standardized interfaces

as a proficient c programmer you should know that creating good interfaces takes strategic thought and experience, especially you have to design them in advance
these skills are rarer than you think- since you seem to think everyone can do a good job in c

Have you heard of something called AI? It's like this program that COMPLETELY ELIMINATES THE NEED TO COME UP WITH AND TYPE OUT CODE MANUALLY. You should check it out, it's quite nifty. Some are even saying it's the future of coding.

>>106906999
shutup marketingroid retard

>>106906932
>ai slop response

>>106906999
Developers that use AI are demonstrably slower and less productive than those who don't.

https://arstechnica.com/ai/2025/07/study-finds-ai-tools-made-open-source-software-developers-19-percent-slower/

AI only impresses nocoders since they don't program anyway and can't tell good from bad.

>>106907021
no, thats how you talk when you're iq is > 100

>>106906879 (OP)
>faster development cycle
Actually its exactly the opposite. For any non-trivial application, you'll spend lots of time in C reproducing whats already "in the box" with C++. Strings are one good example, vectors are another.

>reduced complexity
I understand the argument, but again, the complexity on the developer is significantly less, with in most cases only a very minor perf tradeoff (or even none at all). Again, this is presuming you've actually taken the time to master the C++ standard library.

>>106907652
if were talking about serious c use, then were talking about the cases where the standard libraries dont cut it
so your first argument is countered by the fact that one has the implementations for thigs like vectors or strings in their codebase.
especially strings, null termination with no over-allocation is a terrible hit to performance

and the second argument is ocuntered by, well, the standard library not being used in that project

idk, im not op, maybe he has something else in mind
but that is how i see things.
the usecase for c is when you need more than standard solutions.

>>106907652
>For any non-trivial application, you'll spend lots of time in C reproducing whats already "in the box" with C++.
Truly bizarre how nocoders still believe you can't use libraries in C.

>>106908856
Or AI.

>>106909992
Only blogposters use AI for coding.

>>106906879 (OP)
nice blog post

>>106907701
Ehh, doesn't really matter what your use-case is in my experience. Data structures are still data structures, whether you're crafting a soundfile or a database. Algorithms are still algorithms, whether you're devising an encryption scheme or a vidya renderer.

Use what's already been provided for you, in a standardized way...and that has been banged on rigorously for decades and at industrial scale. Simple as.

>>106908856
Lolnou.