mahsu
Re:MariOCaml: HTML5 Mario, written exclusively in OCaml
on Sunday December 20, 2015 @07:09PM (#10768873)
jsoo certainly takes some getting used to, especially when it comes to actually having to care about the return types of things. Online documentation is painfully sparse and the ocaml type checker was vague at times, so there was quite a bit of trial and error. It does help that all the library bindings are parallel to their javascript counterparts.
Pattern matching with Ocaml is definitely a plus :P, but I definitely felt that working with Ocaml was substantially more challenging. Especially since none of us had prior experience in game development, much less functional game development, the code we produced was riddled with mutability. It would've helped to look at established design patterns first.
Re:MariOCaml: HTML5 Mario, written exclusively in OCaml
on Sunday December 20, 2015 @06:58PM (#10768851)
What would be the best way to throttle fps and ensure compatibility between different refresh rates?
Re:MariOCaml: HTML5 Mario, written exclusively in OCaml
on Sunday December 20, 2015 @06:45PM (#10768809)
The movement is really hacky (https://github.com/mahsu/MariOCaml/blob/master/object.ml#L16...), whereas the actual game takes a more fine-tuned approach (http://s276.photobucket.com/user/jdaster64/media/smb3_physic...). It was tough to keep things simple and use a single set of rules without making everything too floaty or heavy.