3 ms·
I basically did the same things for the same reasons as a kid. I'm very glad to have learned C++, but I bounced off DirectX pretty hard. The API wasn't great (t
by TillE 5y ago
I basically did the same things for the same reasons as a kid. I'm very glad to have learned C++, but I bounced off DirectX pretty hard. The API wasn't great (this was DirectX 7), and the tools available for free were mostly nonexistent. So I never made much progress there.
I'm really glad that kids today can build games with real-world professional tools that are much more friendly, like Unity or Godot.
- mwcampbell 5y agoI learned C without too much difficulty as a teenager, and also began to learn C++ at that point (I doubt anyone ever finishes learning C++), but I abandoned Win32 and MFC in disgust when I briefly tried to learn them at age 18 in the late 90s. Maybe I would have gotten further if I had started younger, or if I hadn't been spoiled by Java first. As it happened, I didn't really master Windows programming until my 20s when I had to do so for a paid job.
- Agentlien 5y agoMy story starts in a very similar manner. I started with C as a kid (9) and tried my hand at DirectX 7 when I was a bit older (maybe 12?) but found the API quite hard to understand. I stuck with making text based games for a few years and moved on to 2D programming using a library called Allegro[0] in high school. It wasn't until university that I came back to 3D programming and learned OpenGL. It clicked in a whole other way than it did as a kid and I've loved it ever since. I even ended up with a career as a graphics programmer. [0] https://liballeg.org/ https://liballeg.org/