So far all postings regarding this point in the opposite direction. No custom "native" runtime, but staying with HTML5/browsers/DOM.
Yeah it's a shame, I hope it all works out with Chromium no longer full of major crippling bugs for C3 to really shine. If I still survive as a gamedev then and the situation is still crap, I'll have to put all my effort to transitioning to Unity.
I understand the concern, not being able to export to console is losing out on a massive market. Its hard to make a smash hit on any one platform, so a more realistic aim is to develop a single game that can ship for XBone, PS4, PC, MAC, Linux smoothly, so that the lower sales on individual platforms combine to create a good income. Also, PC gamers are fickle and it may be that the game we want to make simply do not appeal to that crowd (example The Next Penelope & Airscape), and would work much better on consoles. I can see this factor along as being a major drawback of C2 and it's something C3 should focus upon.
That's why I wanted to launch early next month, I've got a few streamers/youtube players who want to play it and I planned to give them some time to create the content and showcase before the launch later. I've told them all the ETA already. But I can't get these guys to play a broken game.
Well the sooner its fixed, the better for all of us who have been plagued with these issues for such a long time due to how messed up Chromium has been.