Jump to content

  • Log In with Google      Sign In   
  • Create Account

#ActualReflexus

Posted 04 May 2013 - 12:14 PM

The biggest problem with "frameworks" like these is incessant/disruptive abstraction. I started with Game Maker, however, the reason I left it was not solely its incapacity, but the clunky and unhelpful abstraction. When you become a sophisticated programmer, in several ways, going bare bones C++ can be easier than carrying lots of 3rd party baggage around. Game Maker causes a lot of code bloat. So... eventually (even with Unity) I think you'll want to move onto C++.

Edit: Some very credible programmers will even argue that C++ causes code bloat, at least indirectly i.e. language features seem to suggest programmers' paradigms should be more declarative when it's not capable of properly handling what it suggests. They have some good points, but I won't go as far to talk about that issue...


#2Reflexus

Posted 03 May 2013 - 05:51 PM

The biggest problem with "frameworks" like these is incessant/disruptive abstraction. I started with Game Maker, however, the reason I left it was not solely its incapacity, but the clunky and unhelpful abstraction. When you become a sophisticated programmer, in several ways, going bare bones C++ can be easier than carrying lots of 3rd party baggage around. Game Maker causes a lot of code bloat. So... eventually (even with Unity) I think you'll want to move onto C++.


#1Reflexus

Posted 03 May 2013 - 05:51 PM

The biggest problem with "frameworks" like these is incessant/disruptive abstraction. I started with Game Maker, however, the reason I left it was not solely its incapacity, but the clunky and unhelpful abstraction. When you become a sophisticated programmer, in several ways, going bare bones C++ can be easier than carrying lots of 3rd party baggage around. Game Maker causes a lot of code bloat. So... eventually I think you'll want to move onto C++.


PARTNERS