Since all the oldies are posting I thought I throw in my 2 cents.
I love Construct. Both Classic and C2. They're both amazing projects, and it has been such a joy to watch them grow.
C2's IDE feels so damn snappy (apart from the image editor). It's a joy to work with really, even though I've only used it for a few hours so far. The one-click expression editing that classic had is missing at the moment however.
What bugs me about C2 is the lack of a few key features.
-Audio: It's not C2's fault, but let's face it, the audio support is bad in HTML5. You can't change the frequency of sounds the same way that Xaudio could , and I used that feature like crazy. (last time I checked it just made a horribly crunchy noise on chrome, the browser with -supposedly- the best audio support)
-Color filters: it requires an effect, and 3 actions to change a color filter in C2. Not the end of the world, but I really liked that color filters were an integral part of the rendering engine in Classic, with 1 action call. And with no shader performance hit, it allowed you to recolor everything, at will, effortlessly. An enormous plus. Furthermore, Since webGL on mobile is iffy atm, then color filter support in C2 is doomed to modern pcs with FF and Chrome only, perhaps an equal fate to being windows only. Since a game's design and look can depend entirely on color filters, running the game without the effect is not an option.
-Per pixel collision: Not having this cuts out a lot of potential games.
-Slower code performance: Sure, C2 might be able to pump more raw poly's, but what happens when each of those objects has 10 collision checks and 50 conditions per frame?