Need advice
So I'm tied between doing
- A 2.5D sprite based real time tactical RPG using SFML, Chipmunk-Physics, 3rd Party AI and other Libraries in C
OR
- A 3D mesh based *** using the Spring Project in C++
OR
- A 3D mesh based *** using OGRE Yake in C++
OR
- Any other recommendations?
Preferably I want to use C because I consider C++ a crappy language which arose from the depths of hell (http://www.stokely.com/lighter.side/stroustrup.html : shame its fiction), C is a lot cleaner and consistent IMO. I also prefer procedural programming to OOP when it comes to making games.
I know Spodi helped develop a game in C and everything took ages, in my experience with C, refactoring was a little more difficult than in Java and a few extra steps for alloc and free, but apart from that it didn't seem too bad. I could be wrong though because I have never developed a big game in C before.
The other thing is that C will require a lot of glue code, where as the others will be all in one pretty much.
Advices?
I like C, and there are a lot of benefits using it over most other languages, as i'm sure you know but i wouldn't think about creating an entire game with it, that's just my opinion, i really like oop, especially for game programming, it just makes it so much easier to keep building upon without needing to make huge changes to everything, and when you're constantly adding new features and bug finding it could become tiresome. Personally i like c++ because it's an oop language. You could always create your helper methods and such in C then use them in C++. I just think you'll be getting yourself into a lot of work. 
There are 10 types of people in this world - Those who understand Binary and those who don't.
Fair enough.
As for work-load, this is what I don't really understand. I've made (trivial) games both procedurally and object-orientationally, I find that I have 8 times less code using structural programming when following both paradigms strictly. With games I find making changes hardly a problem given good design decisions early on, with business applications this is different, because managers/customers never explain things fully, you find your self making structural changes all the time. Because structural programming is tightly coupled with static un-encapsulated data-structures, a small change can break everything.
This is not to say that either paradigm is better, just that I prefer procedural for games because I'm a fan of small code bases, and flat hierarchies.
And ewww helper classes, not a fan of tight coupling (yeah i kinda contradicted myself there)
Anyway thanks, it got me thinking about certain things that I didn't think about before.
oopsies (I quoted myself instead of editing)
Actually nvm, I think I will go with the 1st option, OpenSource is good but I underestimated how much work original 3d art would need, atleast with the 2d option I can get some help off pixel joint without forking out a million dollars (and then I can design some art myself atleast), I need sleep lol.
I would still like some advice on Game Development in C though if possible, so I know what might be up ahead, and maybe find some more libraries I can use.