# Haxe + Defold = ❤️ **URL:** \ **Category:** The Defoldmine\ **Created:** [February 23, 2019, 5:10pm UTC](https://forum.defold.com/t/haxe-defold/44368 "2019-02-23T17:10:41Z")\ **Posts on this page:** 1\ **Showing post:** 11
**Author:** ![vlaaad](https://forum-defold.b-cdn.net/user_avatar/forum.defold.com/vlaaad/32/10538_2.png) [@vlaaad](https://forum.defold.com/u/vlaaad)\ **Post date:** [March 4, 2019, 12:52pm UTC](https://forum.defold.com/t/haxe-defold/44368/11 "2019-03-04T12:52:46Z")
> [@insraq](#): > > **Type check**. For game development, the feedback loop is naturally not as fast . Therefore, it would be nice to discover more problems in compile time (or better, IDE would usually identify the problem while you are writing it). Defold’s live reload sort of makes the feedback loop faster, but still, with static typing, it would be better. Can you please explain this? I don’t think I understood your argument here. The way I see it, Defold’s [Hot Reload](https://www.defold.com/manuals/hot-reload/) provides a much faster feedback loop than any other engines with static typing because you don’t have to go through stop / build / run cycle, and instead can fix the code and continue with running game. I think it would be very cool if Hot Reload could work with hxdefold (does it?) so we could get best of both worlds… --- _[View the full topic](https://forum.defold.com/t/haxe-defold/44368)._