Day 2.1

The next stage of this chapter was concerned with writing the code for having the game run in Windows. It was a still bore and the author acknowledged that it would be.

It’s basically the code for getting it to open a window, what interfaces it will use connect to the windows, what the icons for the executable with be used, and code on how to stop running the program upon close.

I did enjoy the information just for the simple sake that it helped me to understand that it tries to stop running code when you close an application, not just severs it. That little distinction gives my puny brain a storm of education on why a program gone awry takes forever to close. Years of angry moments just flooded through me with a better understanding. If nothing else, this book will help me teach me more about how programs are going about things. That alone is worth the price to me.

But I still want more. The next lesson is making a game engine. Just reading those words made me think of Doom. The evolutions of games seem to not be in the ability of the programmer, but in the power of the system running it. I bet when the person that made Asteroids first saw it working he dreamed of the games we play and wondered if there would ever be a system fast enough to run all that code.