It's frustrating to be blamed for bugs in other people's software, and that specific iOS audio issue you referenced is the latest and strongest example of this.
I am almost certain the bug is in either Safari or the iOS operating system In this case, it doesn't matter what tool you use: anything at all that runs in Safari will be affected by the same bug. So I guess you can choose a different tool if you like, but you could easily run in to the same bug again, because the problem is in Safari or iOS, not Construct 2.
I didn't even fix the bug, so I can't even take credit for that. It's impossible for us to fix problems in Apple's own software. All I did was found a crazy hack that seemed to work around the bug. So the bug is still there and Apple still need to fix it. Personally I regard this kind of hacking-around-bugs as beyond the call of duty - I'm sure there are companies out there who'd just say "we've reported it to Apple, hopefully iOS 10 fixes it" - but we go beyond that and try to work around (emphasis on work around - not fix) defects in other software we rely on where it's feasible to do so. Note it is not always feasible to do so. The fact this particular iOS bug is worked around pretty much amounts to luck.
Usually someone then blames us for relying on certain tools or libraries which have bugs, but all software has bugs. It's naive to think that if we switch to some other library or framework, everything will suddenly work perfectly. Common suggestions are things like: why not use Haxe? It could have bugs, and we could equally be screwed by its bugs. Why not use {insert library here}? If it's not developed by companies as large as Apple, Google, and Microsoft, it's probably even less reliable. Why not write native code? Operating systems have bugs, and graphics drivers have severe bugs - we have direct experience of that, and they are often far worse than the kind of issue we just dealt with on iOS. They tend to be of the class "all devices with this GPU crash on startup", and there is no diagnostic information whatsoever. In the past we've literally resorted to desperately guessing solutions over a period of days, then ultimately given up. That actually happened with the Construct 2 editor in the early days (it uses OpenGL to render the layout view). Eventually months later we got a tip out of the blue, and we finally managed to work around it. Hardly a reliable approach, but there's little else we can do when it's not our code that's broken.
I know this is super frustrating and when your games aren't working, you naturally look to us for support. However the nature of software development is everything - all platforms, frameworks, libraries - depend on a huge amount of third party code, and that code is as imperfect as everything else. It's implausible to expect any software company at all to magically fix everyone else's code. It affects everyone, regardless of their technology choices.
FWIW Scirra has been larger than just me for a while now. Check the team page. We should be growing again soon as well.
its not other people software it's your engine which is not fully capable , so face it and admit it
c2 worst problem is html5, if it was native there was no problem ! or if there was then we could fix it.
but , i like c2