If that's how someone is using their "game making" tools, they either haven't truly mastered them or the tools they are using are far far too basic of a tool to do anything useful.As for my criticism of GM's, as I said, they're an excellent gateway into the world of programming and great teaching tools, but they only go so far. Sure, it's my opinion, but you shouldn't rest on your laurels if you master a GM - you don't *really* know what your program is doing, you're just slapping together pre-made statements that mean nothing outside the obfuscated layer of abstraction.
As for limitations enhancing creativity, I call nonsense - the only limiter of your creativity should be your imagination. Instances when limitation gave birth to a more enjoyable final product are few and far between. I don't like limits, I like having more resources than I could possibly spend because I don't want to worry about how to implement something, I'd rather spend that time making more content. Optimization is not a creative use of your time, it's a necessary evil. The less problems you have to deal with when programming the better, platforms already impose real-life limitations of hardware, nobody needs additional made-up limitations in their life.
It honestly sounds like your actual experience with these products is relatively limited to a select few rather basic ones you've tried in the past.
I keep pointing out how it's best utilized in CONJUNCTION with an actual programming language or as an IDE of sorts. There's no reason to use one if it doesn't benefit you personally, but these tools do have their place.
As far as limitations enhancing or detracting from an end product, I think we kind of agree that it's a bit theoretical and subjective.
As I've stated I'm not arguing it universally causes creativity in all instances, I'm simply arguing that it isn't inherently a negative thing as it can be beneficial in some cases.. and as previously mentioned, often self inflicted limitations are used for design choice.
