heaps VS miso

Maybe the engine used for Dead Cells, https://heaps.io ?

I've personally had a very good experience with Haxe and Haxeflixel (https://haxeflixel.com/) although Heaps (https://heaps.io/) seems to be more popular nowadays.

Haxe is very nice as a language, can easily cross-compile to a lot of targets, Haxeflixel is heavily inspired by some Actionscript framework and has a lot of goodies. Maybe Heaps is more mature, up to date and allows for more advanced features.

Not really the worst, but you can say my least favorite, and that would be heaps.io

Yeah I think it's ideal for 2D development. Look into heaps.io . . you might like it! These days it seems the best source of community for haxe is in their official discord server.

Many frameworks will let you export for the web, even if you don't code your game in JS. Unity, Godot, Bevy(?), heaps.io ... the list goes on and on.

It takes a little while to get comfortable with heaps.io, largely because tutorials in the Haxe world are pretty limited. Here's a good place to start:

I'm going to go out on a limb and say that most people use Unity or Godot for jams these days. But as long as your framework exports for the web, you should be fine. Personally, I use haxe and heaps.io, but it's a bit of an outlier and probably requires learning a new language on top of learning a framework.

Patching jsaddle by applying this commit made JSaddle usable in Firefox for me, but it has the downside that preventDefault/stopPropagation no longer work (see this issue for more info).

Miso does support jsaddle, docs mention this under the "Live reload with jsaddle" section, although it could be more prominent.

For those interested in DOM-related benchmarks using GHCJS. Miso has some benchmarks here: https://krausest.github.io/js-framework-benchmark/current.html (Ctrl+F `miso`)

ghcjs is the way to go for you, and soon it might be asterius. i do not know how hard it is to set ghcjs up without a framework. but frameworks like obelisk (based on reflex-dom), shpadoinkle, and miso automate that for. i personally like obelisk for its functional reactive programming but it can get awkward and get in your way. so if gui programming is just a means to the end of this one small application and you are not really interested in it nor functional reactive programming, shpadoinkle or miso might suit you better. miso implements the elm architecture (also "TEA", "functional model view controller") and shpadoinkle implements something directly equivalent to the elm architecture. but shpadoinkle achieves more composable widgets by minimalizing the elm architecture. so i recommend shpadoinkle for its better concept although miso is more mature.