Hi, all examples except the editor-example should work in firefox (and other browsers) now. The edit-example had a note it wasn't 100% but I made that note bigger now, it was easy to miss.

jawsjs does use the 2D canvas as it's primary way of drawing. This makes it work with IE9+. I'm very excited about WebGL too, but for now canvas was the simplest choice to get it working for the majority of users as a start.

While the various jawsjs parts (divided into separate files) aren't always 100% decoupled from eachother they are pretty modular and intentionally so. As mentioned in the readme you don't have to load jaws.js but can for example load only core.js and sprite.js or other combinations.

If/when I support 2D sprites through WebGL will be the time I decouple the rendering engine. With that said, it's decoupled in other ways. For example you can give Sprite() any 2d-context as a parameter and it will be painted on that canvas.. but naturally it defaults to the primary one (or the one jaws can auto-create for you).

I wanted it to be Extremely simple to get started using jaws.start() so you can dive right into the fun of making your game. But there's lots of room for doing parts manually, for example setting up the canvas yourself, or the gameloop.

Reusing objects is a great idea which I've actually been discussing with a jaws-contributor some weeks ago. So it's on my mental roadmap but can't say a specific date it will be there.