I have always wondered how so many javascript game framework authors expect anyone to take them seriously when the design, performance graphics and craftsmanship of their demos are often so poor. You might have the most amazing framework ever, but you are not demonstrating that with your demo game at all with its poorly drawn graphics, strangely behaving parallax, flickering tile seams, and a loader that fails to finish half the time.
the demo is your advertisement for the framework. It should ahem demonstrate the benefits of using the engine. Don't you think? If the demo looks bad, the framework looks bad (Often regardless of its actual quality)
The demo was written in the old version of Entity. You can try out the new demo by installing the gem. Those issues have been addressed but I think you're missing the point.
Its the potential of the engine which matters, take a look at the features page to see whats possible.
/show/ me the potential. don't just tell me about it. It's not me that you need to convince. I'm trying to give you some advice here. I am saying: sell yourself better. If there is a better demo available, why is it not live on your website? Is that difficult to accomplish?
More are on the way. My company is actually working on JS games exclusively, and I'm doing a talk on this very subject (I actually briefly mention EntityJS) at SXSW next month. The title of my talk is "Do Gamers Dream of HTML5 Sheep" if anyone is interested.
So how are you making money with HTML5 games? I've made a fair bit of "beer" money with Flash games, but I haven't yet found a MochiAds for HTML5 yet. In-game purchases? Selling access to a less busy server?
We aren't making games comparable to flash/arcade games, they are more similar to games you find on social networks. So, the majority of revenue comes from in-game purchases.