We get a lot of overly broad questions like "how do I make games?"
#1: Programming is the least of your problems.
Game design is its own skill. You can learn to program, draw, model, write music, all of that, and still have no idea how to make a good game. The faster you can get to the task of making games, the sooner you'll learn how to make them. Not program them, design them. You don't even need to program to learn to make a game - people have been doing it with cards and dice for ages.
So if you were to ask me that in person, today, I would tell you "just use Unity with C#." The worst thing you can do if you want to actually make games is get bogged down in language of engine choice. Actually making a game is more important than making a really fast, feature rich engine nobody will use. Why won't anybody use your engine? Because you would need to market it, and marketing an engine is not making a game.
If you're really dead set against using Unity/C#, use one of the OpenGL/C paths. Target a single platform, and forget about Object Oriented Programming. Even C++ is not an OOP language - it's a language with OOP elements which will only get in your way when you're starting out. Remember: Programming is a separate skill unrelated to game design. Whatever you decide to go with don't get stuck in the hows - build it out of a combination of PHP, Visual Basic, and one of those drinking birds if you must. If you want to make a game, actually make a game.
Everything else is a secondary skill!
Q&A for professional and independent game developers
Q&A for biology researchers, academics, and students
Q&A for people who use Blender to create 3D graphics, animations, or games
Q&A for professional programmers interested in conceptual questions about software development
Q&A for medical specialists, students, dietitians, and anyone with health-related questions
Q&A for professional robotic engineers, hobbyists, researchers and students
Stack Exchange Network staging zone, where users come together to build new Q&A sites
Q&A for professional and amateur woodworkers
Q&A for programming puzzle enthusiasts and code golfers
Q&A for members of the workforce navigating the professional setting
Q&A for active researchers, academics and students of physics
Q&A for scientists, academics, teachers and students
Q&A for writers/artists using science, geography and culture to construct imaginary worlds and settings
Q&A for Graphic Design professionals, students, and enthusiasts
Q&A for academics and those enrolled in higher education
Q&A for those who create, solve, and study puzzles
Q&A for scientific skepticism
Q&A for electronics and electrical engineering professionals, students, and enthusiasts
Q&A for information security professionals
Q&A for peer programmer code reviews
Q&A for theoretical computer scientists and researchers in related fields
Q&A for user experience researchers and experts
Q&A for meta-discussion of the Stack Exchange family of Q&A websites
Q&A for students, researchers and practitioners of computer science
Q&A for cartographers, geographers and GIS professionals
Q&A for people studying math at any level and professionals in related fields
Q&A for musicians, students, and enthusiasts
Q&A for dedicated home brewers and serious enthusiasts
Q&A for students and teachers of all martial arts
Q&A for legal professionals, students, and others with experience or interest in law
Q&A for professional and academic economists and analysts
Q&A for mechanics and DIY enthusiast owners of cars, trucks, and motorcycles
Q&A for professionals and students of engineering
Q&A for those interested in logical reasoning
Q&A for scientists using computers to solve scientific problems
Q&A for authors, editors, reviewers, professional writers, and aspiring writers
Q&A for practitioners, researchers, and students in cognitive science, psychology, neuroscience, and psychiatry
Q&A for professional and enthusiast programmers