Honestly, it seems like we are seeing a recurring theme here: the 'major' C2 devs (people like Aurel and sqiddster who have made large, polished games that took a ton of time and work, and are being deployed as commercial projects) are saying that they won't be using C2 for future large projects. Not because of issues with the editor, or even performance in general, but because of two things that Scirra cannot realistically do anything about:
1. Depending on a browser engine (basically, chromium) for export, which could very well break and not be fixed, given that HTML5 games are hardly a priority for Google.
2. Console export. Aurel has as much as admitted he's been approached with high$ offers for Penelope on consoles, and had to turn them down.
Most other users are making comments about performance. I don't think that is a serious issue.
C2, unhampered by faulty exporters, as already extremely fast on PC, and will continue to improve, as it has done for the past 4 years. ASM.JS, SIMD.JS, better support for parallelism...all of these are coming and will benefit C2/3 tremendously. But honestly, most performance issue fall into 3 categories: Poor design, unrealistic expectations, or blaming C2 for faults in the given browser/exporter in use.
So performance will improve...but we will still be using browser engines. And we may never be able to export to consoles this generation.
I think this is a time to adjust our expectations and understand where Construct fits among the available ecosystems. The only reason we have this amazing software, which doesn't cost a mint, is because of all the open source components it is built upon (chromium being one, in that's it's our sole option for desktop export).
Ultimately, this means that the direction Scirra takes, and the perception of Construct, good or bad, is ultimately in the hands of Google, Mozilla, and Microsoft. Three massive organizations who may or may not care about their engines mucking up all our work.
That's the state of things, good and bad.
Even after 4 years, we are still on the cutting edge. Sometimes the cutting edge makes you bleed.