I guess coming from the web world I would call those Game Frameworks, not necessarily engines. Just because he hasnt laid out a proper API doesnt make his game

I guess coming from the web world I would call those Game Frameworks, not necessarily engines. Just because he hasnt laid out a proper API doesnt make his game "run" (as in engine) any less... its still a working game. And it could be used as the engine to power similar type games, even though time and forethought hasn't been put into making that easy (like in the case of a Framework API). So in my mind its still a game "engine". But I see your point, definitely. I never really knew "engines" implied API's and abstraction, but I guess that does make sense. Just the fact that its running in a browser on Webkit kind of implies its an engine of sorts in my mind. Thats just how my train of thought works when thinking about things in the context of javascript/the web world.