[quote:27xutvll]C3 will be what it will be, and I do not think we have a choice in that, nor they have any obligation at all, if C3 is an "upgrade to C2" and that does not convince you, just do not buy it, ashley choice for C2 was html5 only, and while some people see it as a bad choice, they are native engines so buying an html5 one is not something you should have done, ok, there are hiccups in the marketing, but for C3, there should be not the same confusion.
I don't see why you're talking about people complaining about HTML5 here. Personally I have no problem with HTML5, it lets me create games and that's all that matters to me. I just don't see the point in making Construct 3 another HTML5 engine since there's already Construct 2 for that, even if it is going to have major changes, put it in an update, I'd hate to see our purchases rendered moot.
[quote:27xutvll] when in fact you trade off performance for portability and probably reliability. By far, the best solution is to improve C2's engine to resolve any performance deficiencies.
Currently, I don't see any of the games on the Construct 2 front page being made for anything other than PC, with the exception of 'Mortar Mellon'. You can improve C2's engine to resolve all the performance deficiencies all you like, if wrappers like Node-Webkit just release more broken builds like with the jank that's still not fully resolved, that will leave us with a perfectly fine and amazing engine that cannot export any normally functioning games due to non-Scirra companies releasing broken software or possibly even abandoning it.
Ashley, I want to ask you a serious question. What would you have done if, after Google release the Node-Webkit with the jank and all the horrible performance, they shut down and stopped making new Node-Webkit builds and fixes?
We would be left with a broken exporter and basically all C2 users who want to export to computers would be furious, then you'd be forced to make a native exporter either way. We all know how many posts and a couple bug reports were made on just that one "update", imagine if that build was the last we got forever.
I know it didn't happen, but what if it did?
There is a thing as future proofing. In fact, if there was a native Construct 2 .exe exporter or similar, C2 users themselves could probably provide fixes for it just as they provide plugins and effects for the engine.