Ashley - if you read this, when you respond to the idea of native exporters (I could be wrong about this, I apologize if so but it's the impression I get), it seems like you think we're talking about you making your own complete browser engine, because you talk about how you couldn't compete with google or such's team of engineers. We're not. What we want is just native games, no web tech that games don't need. Yes it would make a lot of third party plugins obsolete, but I just don't care as I don't use them that often. i really think html5 is holding C2 back.
I don't believe that it's impossible to create native exporters that work better than chrome. There's thousands, possibly hundreds of thousands of games out there that do exactly that. Chrome is trying to support everything a web browser can do. Games need only a fraction of that. We don't need CSS or PHP or SQL or whatever web tech. Trying to support them all is not an achievable task for a small team, but supporting all of the functions needed just for games has been achieved by many, many small teams out there, including you guys with the native exporter in construct classic.
Yes, it might take a while to code. I understand that C2 is solidly on the html5 train, and it's not good to try to get off a train while it's in motion. However, if someone could be hired to work on it concurrently, then work on the current to do list would be able to continue at the same time and no delay in updates to c2 would occur.
However, even if you can't find someone to help, then even working by yourself I think when most or all of the stuff on the to do list is done, then a switch to native should happen. I don't know if 3d could be considered at that point as well, but I also think it should be incorporated, and that might be a good place to do so, or to at least lay the framework for it to be implemented later on.
This could be nicely done same way like official SpriteFont plugin was made.