# So I made this other game... (Nonaga)

**URL:** <https://discourse.elm-lang.org/t/so-i-made-this-other-game-nonaga/8200>\
**Category:** Request Feedback\
**Created:** [February 23, 2022, 5:14pm UTC](https://discourse.elm-lang.org/t/so-i-made-this-other-game-nonaga/8200 "2022-02-23T17:14:36Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![axelbdt](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/axelbdt/32/4404_2.png) [@axelbdt](https://discourse.elm-lang.org/u/axelbdt)\
**Post date:** [February 24, 2022, 1:37pm UTC](https://discourse.elm-lang.org/t/so-i-made-this-other-game-nonaga/8200/3 "2022-02-24T13:37:35Z")

</div>

Thanks for the kind words, and for your answers as well 🙂

I’ve thought a bit about having event handlers at the wrong time and actually expect the approach to be cleaner after all: it would gather the logic in the update function and allow it to be checked by the compiler to some extent (e.g exhaustive pattern matching). I think removing the event handlers makes the view code a bit hairy and might create an “implicit state machine” problem.

I’ll try it out!

---

_[View the full topic](https://discourse.elm-lang.org/t/so-i-made-this-other-game-nonaga/8200)._
