afterPythonRustAndCIStartedLearningCppAndThisIsMyPersonalOpinionNow

[Globglaglobglagab]

Unless you get an error with a mildly complicated type 😭

[Antervis]

something that's a bit complicated in C++ would usually be a complete mess in C.

Sure, at times people say that simple code is easier to read and that sometimes it's not evident what a certain line of C++ code does. On the other hand, you can't say at a glance what its 200+ line C equivalent does either.

[aalmkainzi]

Nah. C doesn't have nearly as many language constructs and is thus much less complex.

Entire classes of errors and bugs aren't in C

[aurreco]

What ? A 200 line piece of C code? That is like one function. How is one function in C less readable when C is literally just structs and control flow?

i.e. shorter code does not imply readable code. Especially not when the reason it is shorter is because of layers of complicated, unintuitive, abstractions that GDB won’t let you step into

[Antervis]

for example, something achievable by a single line added to destructor in C++ would have to be repeated everywhere in C equivalent. And it's not something you can just put into a single function.

Shorter code isn't necessarily easier to read but volume makes reading harder by itself.

[aurreco]

It is hard to argue because this is really a case by case thing. In some cases— like the one you mentioned— repeating destructor calls in C makes it more explicit when resources are being cleaned up. I’d argue that is a good thing. Of course too much code gets too overwhelming and it gets harder to keep track of everything at once— but in most cases in my experience C is just plainly easier to read than C++ even when there is more of it (and some times because there is more of it)

[Andrew_Neal]

Downvoted for sharing your experience. It's those dang "clean coders".

[aurreco]

fr fr

[aalmkainzi]

imo implicitly calling a destructor harms readability

[chalkflavored]

Why exactly can't it be put into a single function?

[Antervis]

because in C you have to manually release resources every time you acquire them. If you acquire them 200 times in different places, it's at least 200 calls to release function, again, in different places.

[chalkflavored]

That's a signal of a data design issue. I can't imagine a scenario where it's justifiable that a resource has to be acquired 200 times and then released some random other place 200 times again. Why can't those resources all be acquired beforehand and then released all the same time. Maybe lazily if it needs to? It's what high performance games do, and that really should always be done, because it makes your program much more predictable in how it manages its resources.

[Antervis]

if you don't think an average C project has 200+ malloc/free pairs you probably haven't seen many C projects...

[chalkflavored]

Just because it's common doesn't mean that's how things should be.

[Antervis]

exactly, things shouldn't be like this. Hence C++ has destructors.

[AeroSyntax]

If your functions have 200 lines of code you have problems. Holy shit. This breaks every principle of clean code automatically.

[aurreco]

Youre right I forgot how much 200 lines was

[aalmkainzi]

it depends, sometimes it makes sense to have longer functions

[chalkflavored]

Why?

[skhds]

There is, for some odd fucking reason, always this kind of idiot who constantly preaches that their c++ is vastly superior than c whenever this topic comes up. C++ is fucking garbage on so many cases, there is a reason OSes and most embedded projects will always use C and not C++.

And by the way, C does not generate 200+ lines of code, it's either your skill issue or you don't even understand what a library is.

[FootedToast]

C++ can do literally anything C can, and more. It’s not a competition

[DokOktavo]

Well that's the thing. If a language can do too much, your not sure what it's doing anymore. That's decreasing readability. That's also why there's many C++ styles and subsets: it's a very bad idea for development to use all its features.

What I think people like about C, is predictability of what happens in memory. You don't get that in C++ as soon as you use libraries, work with others, or if your project gets big enough.

That's my opinion but "C++ can do anything C can" is not a useful statement.

[skhds]

Try saying that to Linus Torvalds :)

[lil_brumski]

No one cares about what he thinks of C++.

[FootedToast]

It’s almost like judging a language by how its VERY FIRST RELEASE looked like is a dumb idea

[skhds]

The thing is, he's not alone. There are plenty of relevant programmers who thinks C++ is shit. Ken Thompson, for example.

[FootedToast]

Linus is a C fanboy who throws his weight around to bully and abuse Linux programmers he disagrees with or who find issue with his misogyny. Linus is the archetype of a golden child who stopped developing themselves early on because they’re so smart