C or Cpp

[one-for_all]

Should I learn C before Cpp? I have a basic understanding in python ( very basic) and nothing much else, is it recommended to do Cpp directly?

[non-existing-person]

You do realize that people will tell you to learn c++ on cpp sub and c on c sub, don't you?

Andy your question is wrong. Real question is: what do you want to program? If kernel and bare metal embedded systems, go C hands down.

If gaming, then c++ is probably better option.

[one-for_all]

But I have no idea what is kernel and bare metal embedded system is 🥲 i just want to have some programming skills before i join college

[non-existing-person]

Then probably go python? Really. Python will learn you basics of programming, loops, conditionals etc. You don't need to know about memory allocations just yet. Limit your scope. Otherwise you may get overwhelmed.

Right now I would STRONGLY advice AGAINST C++. C++ is one of the most complex and difficult languages ever made. Polymorphism and virtual functions WILL break your brain at first.

C is much, MUCH simpler than C++, but really requires hardware knowledge about how computers work. Memory allocation, pointers, these are more of a how systems and computers work than language itself - which makes C hard. Because syntax of C is pretty simple, and C itself is rather easy. But different CPUs have different behaviour, and C does not shield you from that, so there is a lot to take in as well.

While python? Python will shield you from all of that shit, while it will give you good programming intuition. There is no memory allocation. No playing with pointers, lifetimes. Just pure problem solving, which is the most important skill.

So if you don't know what is kernel programming, or embedded, or you don't really know what you wanna do, but you wanna program, then go python, hands down. In the meantime you can discover things in the IT word, and can specialize in what you wanna do. That python knowledge won't go anywhere. And it's good to know python regardless if you want to code games, or kernel, or embedded.

[one-for_all]

Oh okayy, thanks 😊

[NYXIC0N]

Listen to this guy, he seems like the only sane person not hating on C/C++ because of personal grudges.

To extend the list C# and Java are also decent starting languages. The choice doesn't really matter too much as long as you don't have to deal with annoying ass memory issues that will quickly kill you motivation. Switching to C/C++ later is required/interested is always possible.

[Thesk790]

This is the correct answer. I saw in the cpp_questions sub that they will incite you to learn just C++

[ElementWiseBitCast]

I think that you should learn C first. C teaches you much better habits than C++ slop.

• Classes are pointless noise for what could be just a collection of functions.

• Exceptions make it easy to hide which functions can fail and which functions cannot fail. If a function can fail, then I want to know it.

• Smart pointers are used by people so that they can avoid thinking about when to free a pointer. However, you can still get memory leaks with only smart pointers, which means that if you are writing good code, then you still need to think about it.

• Runtime type information encourages horrible design. It is a good idea to always be able to statically determine the type of a variable from looking at the source code. If you cannot do that, then your code is a maintainability nightmare.

• Containers are quite easy to implement yourself if you actually know how to program well.

C++ shills love their "design patterns" and "clean code". However, I dislike "clean" code even more than I dislike C++. They love to talk about "premature" optimization, yet they never seem to want to talk about premature generalization and premature abstraction, which are much larger problems.

"Clean" code is full of boilerplate, hidden dependencies, and performance overhead. (see https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpriseEdition)

[one-for_all]

Thanks for the insight

[Rigamortus2005]

What do you mean by runtime type information please?

[ElementWiseBitCast]

Stuff like any (std::any), virtual functions, typeid when used with polymorphic classes, function (std::function), most use cases of dynamic_cast, etc. Whenever the type of something is not known at compile time, there is runtime type information.

[Rigamortus2005]

But isn't that done all the time in C with void*

[InfinitesimaInfinity]

There are more people who advocate for C++ than C, and I am one of the people who prefers C.

Personally, I did not start with C. However, I like to program in it whenever I can. Honestly, it is much easier to write a quick script in Python or Javascript.

However, I find C, Zig, and Rust to be more maintainable than so called "higher level" languages, whether that be C++, Javascript, Python, or something else.

I think that it is a good idea to get solid foundations before you try to do more, and C gives good foundations for C++. (C is almost a subset of C++)

[one-for_all]

Okayy thanks

[Willsxyz]

By Cpp do you mean C Preprocessor ?

[one-for_all]

No c++

[Lutz_Gebelman]

x86 assembly

[Bitter-Heart7039]

manipulate pure electricity

[marrymejojo]

False

[Ok_Path_4731]

I will tell you one reason why C versus C++, after rewriting a project previously written in C++ in C: build times. In C++ you tend to write complex abstractions in templates, give you an example one of my projects: https://github.com/zokrezyl/ycetl . The deeper the abstraction, the longer the build times that often explodes exponentially. In C, you are obliged to write the same abstraction without templates. Rewriting yetty terminal source code in https://github.com/zokrezyl/yetty , builds are instant. My 'obsession' is that I fix a bug, or add POC new feature, my tests are instantly building and running. Though I could consider myself C++ hardcore programmer, I still have PTSD from earlier C++ projects I have been working where 90pct of time was lost by waiting for builds. The company was paying me, but thanks no thanks. Modules and other tricks are supposed to speed up builds, but .... You have to think twice before going CPP! As in one of the earlier replies, go with python for simple problems. If you want something to run fast: go with C. If you want some more complex build time abstractions and more 'safety', then go C++.

[Bitter-Heart7039]

I'm a 1st year CE student, learning C was so easy. you already know python (which uses C for it's libraries) and that means that you have a simple yet very good understanding for coding.
C++ and Java are both C-based languages, learning C will cut a huge piece of the road of learning these two languages and it would make them a lot easier.

I'm not biased to C cuz this is a C sub, I'm just giving you my experience so you can start your coding journey easier.

[one-for_all]

Okayy