I have noticed a few things about construct 2. I have a feeling you all have too- if you have tried to make any large projects... (large being a relative term, obviously SC2 is large but for the sake of construct lets say large is MetroidFusion/Yoshis island)
Construct2 is really fast to work with. I was sold on it a day after I bought it and I still haven't changed my mind about how awesome it is. That having been said, there is a number of things that start to get in the way/ decrease potential productivity. These are....
1. Events are tied to a singular project. It is next to impossible or practically a nightmare to try and re-use functionality from one game to another. As it is, event sheets can get increasingly long as a project goes on. Sure you can split them up and call them, but that isn't very handy. It's like construct was made for smaller games and hasn't realized its potential.
2. Functions need to be able to be called in the same manner as referencing an object- that is, they need to be included in some sort of conclusive, auto-completed menu system. As it currently works, you have to remember all your function names and spell them correctly... not to be high and mighty, but as a programmer that is computer work. having function names not being able to be in a hierarchy of calls is also silly. Having to type in "player_somefunction()" every time you need to call it can get old. Especially when you end up typing "plyaer_somefucntion()", or something similar. Instead of the event editor telling you you have made a bad call, you spend precious time trying to figure out a logic error that doesn't even exist.
I will still use Construct2 for small projects and prototyping, but I can't see trying to undertake a mammoth project again.
Any Thoughts - agreements/disagreements ?