![]() Abusing inheritance or not making proper use of aggregations. The problem is for some reason too many programmers just don't do OOP well. Tue 30th Mar I think my major qualm with C# is that it kind of forces you into object oriented programming but I don't really like the idea of programming paradigms in software engineering and think they have held the field back greatly.īut I think the concepts introduced in OOP can be quite nice when applied well.Having everything in a single environment is pretty nice when it comes to having a quick workflow. It's certainly not perfect, but for small projects it's absolutely fine. I've used it for nearly 30 years now, including on some very large pieces of software, so I've got a pretty good feel for what's good and what's not so good.įor my own games (all of which are pretty small of course) I've run the full gamut of technologies from my own engines written in C++ and OpenGL, Unity, SpriteKit all the way to Game Maker Studio 2. There's still a lot to like about C++ even if you completely ignore OOP with the revisions to the language over the last 10 years. They almost always end up bad and difficult to understand. Especially when it comes to things like deep inheritance hierarchies etc. On OOP, it's been interesting to see how generally people are moving away from the extremes of it now. ![]() ![]() I also agree that once you get to the point of making optimisations to avoid the worst parts of your technology stack then you should move to something more appropriate (as in the Unity case). If you're working on a large project then you're going to want more control which will of course require a language like C++. Personally I think Monogame is quite a nice library for smaller games (I was a fan of XNA). As you say, there's also the option of using a subset of the language too.
0 Comments
Leave a Reply. |