Nice!

For me, slow progression is important to actually make the concepts "stick" in the brain, so do make sure to take your time in the journey, and not do the whole course in few days.

I would heavily reccommend to experiment with the code yourself, see it crash and error out and really get the "why" it works (not just how to do it in that case). For example, you can pass 3 parameters to a function?

Another great tip is to have a small project you are passionate about yourself: a card playing game (on the terminal, without graphics), an interesting math simulation, or a small program usable via terminal.

C++ is hard. If it's too frustrating consider python for an easier introduction (there are no pointers there!), and you can still switch to c++ later. All mainstream programming languages work more or less the same, and the programming skills transfer very well between them!

Keyboard still on deck homie. I will send it.

it carries around a lot of baggage from the last 40 years.

Cppfront2 is an interesting experiment that looks at an approach to solve that problem without a hard break. While my C nostalgia is offended by the syntax, I'm quite fond of it. Bornje's pet topic of 'profiles' is another but hasn't landed much yet.

Agree on that. It cuts both ways. On the one hand, it gives you access to a fuckton of libraries so that you can chose the one that best fits your use case. On the other hand a lot of those libraries don't use modern C++. And I haven't even started on things like the win32 API, which is essentially a C library masquerading as a C++ API.

That's essentially the thing with C++: when you're chosing which library to use, the level of C++ should be a factor in the decision making process, along with things like performance and functionality. And if I do end up using a library that was written for an old C++ version, I create wrappers for the things I use the most to bring it to the level of C++ I'm working with. Sometimes it's also interesting purely from a learning perspective. That's what I did for a lot of the win32 APIs I worked with.

You mentioned tutorials - I learned C++ from learncpp.com, and I couldn't recommend it more. It does a really good job at going deep into the technical stuff, but also understanding and using the most modern features of the language, as well as best practices.

carries around a lot of baggage from the last 40 years

cries in C stdlib

I hate null terminated strings. Though the rest of just C without the "pluses" is nice. Nobody really kept adding new things unlike in C++, it's just mostly the good old stuff.

Anyways

GTK basically asks you to write plain C

From my perspective, glib is all possible languages at once implemented as C macros. What you are actually writing is technically valid C, but I would consider it "glib language" lmao.

C++ is a lot of things but elegant and safe are not words that come to mind. C++ has far more issues than regular C.

Best option would be to use something with memory safety

a lot of languages support qt6 though

Props to you for learning C++, its a neat powerful language, although it has grown quite overcomplicated through the years.

Though if you want something a bit easier, you can also use Python for Qt development through the PySide6 library. It is one of the officially supported Qt languages alongside C++ and JS. I've personally used it for a few programs and it works wonderfully, it is one of my favorite ways to make GUIs for myself, it just works™

True, it was just a recommendation because for me it made more sense this way around. Like objects are just structs with function pointers and some compiler magic to ensure private and publicness, polymorphism is just unions etc.

that was not what i expected at all when your example was rofi. sounds more like the kde app launcher.