Well apart from the fanboyism/hate relationship that there is currently (which I don't get but whatever), PixelPower does have a point:
Scirra does tend to not fix bugs coming from a third party ("Close as won't fix" anyone?), which break our games multiple times in the past for sometimes a very long wait (the jank/stutter), imagine a bug similar happens and break C3, oh my god, I hope they have a plan for that, because telling users not to update their browser would be downright stupid.
Construct Classic = windows + directX. Feature creep all over the place. Abandoned, left unfinished. Left for community to extend and "clean up", after it's sinkage.
Construct 2 = HTML5, new tech at the day of release. Jack of all trades - master of none. Is being maintained but not really extended. Far from "finished" state, but its Devs claims otherwise, of course. If not for community workers such as Gigatron, Rex, Pode, R0jo and others - it would met CC fate already.
Construct 3 = yet again, a new approach, new tech and experimentation.
It really doesn't take to be a rocket scientist to spot a reoccurring pattern over here.
I am not bashing Scirra or Construct brand. If that would be the case, I would left this forum long time ago. Yet I am still here, after all those years (8 years as a user, almost 7 years with a forum account).
That's because Construct, be it Classic or 2, is still one of the faster if not THE fastest engine, in terms of rapid prototyping and fluid workflow. But the real problem, every single time, is when you are close to finishing your game or right after doing so. When you have to publish it. And I am not talking about regular platform-specific hassles like paperwork, size limits, and stuff.
Lack of proper Steam API, no Node Webkit export customization leaving you with a default mess that you can do nothing about, all game's assets RAR'ed into simply unprotected archive for anybody to take, not being able to change exe icon by normal means, not being able to even rename that ugly nw.exe, Intel slowly dropping support for Intel XDK, no 1st party API for Flash Portals games, shaders and plugins working in the editor but not working upon export, shaders and plugins not working in the editor WORKING upon export, constant 3rd party reliance whenever you actually want to send your baby into the world, random unknown FPS drops/memory leaks. 95% of features request/bug reports closed because "won't fix"/"wont add cuz reasons/little priority" (aka busy with C3 so "up yours!"), and games randomly working or not working at all on various OS'es, browsers, setups.
One can digest only so much before leaving the boat or going PixelPower hehehe.
I am here because I still, "after all this time", care. Care and hope.
Care - about Construct.
Hope - for a miracle.