Learning C++ in 3 easy steps: 1. Read a book about C 2. Make a bunch of small projects in C for a few months to a year 3. Switch to C++ and experiment but only bother learning about the things that you actually find useful
Joined Low Level Game Devs Discord once, its full of conspiracy theorists and people who dunk on you when you cant code. "Bro do it like that are you stupid?"
0:30 yes, but people who were familiar with visual coding in past , struggled and spent too much time choosing the path of learning actual language. I was actually one of them because I was familiar with godot's , unity's , unreal's visual languages. But eventually I realized that I have to learn actual language if I want to be adaptive and fast at game development.
I am learning C++, and after that, I plan to start with SFML. But C++ is not so easy, especially because I was learning Python before that. I found good tutorials 186 lessons in my native language, however, sometimes I just lose motivation to finish this playlist. As far as I know, OpenGL is for 3D graphics. Why do you use it for your 2D game? Or with OpenGL do you also need to create everything from scratch?
I've never made anything big in C++ but why do you want a 20k line file? Those are always hard to navigate in my experience. Once I hit 5000 lines it starts to get unwieldy and I break it up. Compiles time are a problem too right? If you have smaller files you only compile the file which changes and the others are just linked in. Maybe that doesn't so easily in C++ though.
@@SoDamnMetal 5000k is the high end but depending on what's in there it can be fine (for me) and especially if breaking it apart causes additional confusion as to what is where.
@@ensuretime I've been programming for over 25 years and I see no reason to have such rules. It all depends on if YOU can navigate the file and find what you need, and of course compile times. If you're using some language that's slow to compile and multiple files help I would break things up for that reason alone.
I tried to make my own engine with SFML and I hated that so much. Went back to Unreal and the C++ there is so forgiving and along with BP oh god its so much easier
"learn the language" is dogshit advice if you don't give an example of a course that teaches it well. The actual problem is that there aren't many places that teach languages well and are applicable to games, I've looked many times and 99% are OOP BS that will trap beginners in the bad place.
here's a better advice 1) learn c (not c++), there are some good c teaching resources (I've actually learned c with sololearn, there's also a pretty good course by caleb curry (I had previous programming experience including basics of c++, your mileage may vary)) 2) do some projects, fail miserably, learn how to use your system apis, send some bytes over the wire, write a cli audio player, maybe a little game with sdl or raylib, get to know build systems and why cmake sucks 3) watch (at least parts of) the handmade hero saga steps 1 and 2 are optional and may take different shapes but step 3 is mandatory (I will call the police if you don't)
Learning C++ in 3 easy steps:
1. Read a book about C
2. Make a bunch of small projects in C for a few months to a year
3. Switch to C++ and experiment but only bother learning about the things that you actually find useful
Joined Low Level Game Devs Discord once, its full of conspiracy theorists and people who dunk on you when you cant code.
"Bro do it like that are you stupid?"
0:30 yes, but people who were familiar with visual coding in past , struggled and spent too much time choosing the path of learning actual language.
I was actually one of them because I was familiar with godot's , unity's , unreal's visual languages.
But eventually I realized that I have to learn actual language if I want to be adaptive and fast at game development.
I am learning C++, and after that, I plan to start with SFML. But C++ is not so easy, especially because I was learning Python before that. I found good tutorials 186 lessons in my native language, however, sometimes I just lose motivation to finish this playlist. As far as I know, OpenGL is for 3D graphics. Why do you use it for your 2D game? Or with OpenGL do you also need to create everything from scratch?
I've never made anything big in C++ but why do you want a 20k line file? Those are always hard to navigate in my experience. Once I hit 5000 lines it starts to get unwieldy and I break it up. Compiles time are a problem too right? If you have smaller files you only compile the file which changes and the others are just linked in. Maybe that doesn't so easily in C++ though.
5000?!? 500 is my limit for navigating a mess, though usually it's less (200-350ish).
@@SoDamnMetal It's common for more experienced programmers to suggest a limit of 1k per file, more than that should be refactored/broken into pieces.
@@SoDamnMetal 5000k is the high end but depending on what's in there it can be fine (for me) and especially if breaking it apart causes additional confusion as to what is where.
@@ensuretime I've been programming for over 25 years and I see no reason to have such rules. It all depends on if YOU can navigate the file and find what you need, and of course compile times. If you're using some language that's slow to compile and multiple files help I would break things up for that reason alone.
20k is far to big, i think 1000 is my max but i've only ever gotten to 500
I tried to make my own engine with SFML and I hated that so much. Went back to Unreal and the C++ there is so forgiving and along with BP oh god its so much easier
"learn the language" is dogshit advice if you don't give an example of a course that teaches it well. The actual problem is that there aren't many places that teach languages well and are applicable to games, I've looked many times and 99% are OOP BS that will trap beginners in the bad place.
here's a better advice
1) learn c (not c++), there are some good c teaching resources (I've actually learned c with sololearn, there's also a pretty good course by caleb curry (I had previous programming experience including basics of c++, your mileage may vary))
2) do some projects, fail miserably, learn how to use your system apis, send some bytes over the wire, write a cli audio player, maybe a little game with sdl or raylib, get to know build systems and why cmake sucks
3) watch (at least parts of) the handmade hero saga
steps 1 and 2 are optional and may take different shapes but step 3 is mandatory (I will call the police if you don't)