No one's bashing construct 2 or HTML5.
Construct 2 is the best game making tool out there, with the best workflow, which is not to say it's perfect.
HTML5 is really good now, and can deliver some impressive results, though we aren't there yet in terms of portability. There are many limitations to what can be accomplished, even in a beefy desktop running a modern browser.
Mobile, however, isn't there yet. You can't make anything but simple puzzle games in there - meanwhile, other engines with native exporters perform a lot better. Sure, they aren't as capable and working with them is a convoluted mess, but the end product is often more performant.
I don't know why people are getting all defensive. I love construct 2 and scirra, but we're not there yet in terms of multiplayer and semi-professional mobile development. Blame it all on HTML5 and phone manufacturers (especially apple - I mean, their stuff costs double the price of an android/htc/blackberry/whatever with HIGHER specs and even with all that money they still can't get their act together? I honestly don't know why people buy their stuff).
In regards to mobile HTML5, Blackberry is putting a lot more effort into it than everyone else, and I'd recommend developers stick with them - the environment they're creating for us seems far less toxic than apple or microsoft's alternatives. Android is pretty okay, Google is very competent and mobile chrome is great. Firefox mobile shows promise as well, especially if you want to focus corporate, low-end or edu.
Do notice that Ashley can't do anything about any of this. The strategy of integrating third party exporters worked to some extent (in that we now know which technologies suck and which show some promise), and shows the goodwill Ashley has in supporting us in that area, and how he'll do everything he can to make it better (compare that to other game making tools, which just don't care, and spend years with updates that amount to little more than bug fixes. @Konidias will know which one I have in mind specifically). The most recent versions appear to be focusing more on the core product, with new features to help the core engine, and that's a relief for me.
It says a lot that, even when working in large projects, ALL THE ROADBLOCKS I've encountered so far, NO EXCEPTIONS, have been in regards to HTML5. It was NEVER construct2's fault, and on the few times construct didn't do something I wanted it to do, I fired up my development kit and made a plugin/extension to fix it.
I'll end up by agreeing with Konidias, though I'll disagree with the title - this is not "the sad truth of construct 2", but "the sorry state of HTML5 right now, especially in mobile".Fimbul2013-02-07 22:12:11