For example, if HTML5 performance gets good enough that an EXE exporter can only get a 10% performance edge, then an EXE wrapper around the HTML5 runtime should be perfectly adequate (possibly with a plugin to access Steam API features).
Is making an EXE wrapper much more feasible than a full exporter? And if so, are you more willing to work that in more quickly?
Again, I'm just trying to decide where to go from here. There aren't many places outside of Steam that are suited for products that aren't simple and casual, so if it doesn't look like I can get my project onto Steam, I'll put it aside and work on something else until I can. No pressure or anything, and I don't wanna sound like I'm attacking you, but... this stuff is important for us devs to know, y'know? <img src="smileys/smiley5.gif" border="0" align="middle" />