# The Joy of Haxe

**URL:** <https://community.haxe.org/t/the-joy-of-haxe/1199>\
**Category:** Showcase\
**Created:** [October 19, 2018, 7:24am UTC](https://community.haxe.org/t/the-joy-of-haxe/1199 "2018-10-19T07:24:55Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![meek](https://community.haxe.org/user_avatar/community.haxe.org/meek/32/471_2.png) [@meek](https://community.haxe.org/u/meek)\
**Post date:** [October 19, 2018, 7:24am UTC](https://community.haxe.org/t/the-joy-of-haxe/1199/1 "2018-10-19T07:24:55Z")

</div>

I’ve written a post about the adoption of Haxe on [FontStruct.com](http://FontStruct.com)

[https://medium.com/@fontstruct/the-joy-of-haxe-84f933f4b859](https://medium.com/@fontstruct/the-joy-of-haxe-84f933f4b859)

I’ll be tweeting about it later but posting here first.  
I’ve also open-sourced part of FontStruct’s font generation module:

> **[FontStruct/fonthx](https://github.com/FontStruct/fonthx)**
>
> Font File Generation in Haxe. Contribute to FontStruct/fonthx development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![Simn](https://community.haxe.org/user_avatar/community.haxe.org/simn/32/388_2.png) [@Simn](https://community.haxe.org/u/Simn)\
**Post date:** [October 19, 2018, 7:55am UTC](https://community.haxe.org/t/the-joy-of-haxe/1199/2 "2018-10-19T07:55:52Z")

</div>

This is a really nice article. Thanks a lot for this!

---

<div class="post-metadata">

**Author:** ![AtomicPair](https://community.haxe.org/user_avatar/community.haxe.org/atomicpair/32/93_2.png) [@AtomicPair](https://community.haxe.org/u/AtomicPair)\
**Post date:** [October 19, 2018, 8:31am UTC](https://community.haxe.org/t/the-joy-of-haxe/1199/3 "2018-10-19T08:31:08Z")

</div>

Agreed. Insightful, detailed, and well-written. Nicely done!

---

<div class="post-metadata">

**Author:** ![matan](https://community.haxe.org/user_avatar/community.haxe.org/matan/32/206_2.png) [@matan](https://community.haxe.org/u/matan)\
**Post date:** [October 19, 2018, 8:50am UTC](https://community.haxe.org/t/the-joy-of-haxe/1199/4 "2018-10-19T08:50:49Z")

</div>

Very nice! What is your twitter handle? I’d like to retweet once you post publicly. 🙂

---

<div class="post-metadata">

**Author:** ![meek](https://community.haxe.org/user_avatar/community.haxe.org/meek/32/471_2.png) [@meek](https://community.haxe.org/u/meek)\
**Post date:** [October 19, 2018, 8:52am UTC](https://community.haxe.org/t/the-joy-of-haxe/1199/5 "2018-10-19T08:52:51Z")

</div>

Thanks for the positive feedback! FontStruct is on twitter at [https://twitter.com/fontstruct](https://twitter.com/fontstruct)

---

<div class="post-metadata">

**Author:** ![elsassph](https://community.haxe.org/user_avatar/community.haxe.org/elsassph/32/60_2.png) [@elsassph](https://community.haxe.org/u/elsassph)\
**Post date:** [October 20, 2018, 9:00pm UTC](https://community.haxe.org/t/the-joy-of-haxe/1199/6 "2018-10-20T21:00:05Z")

</div>

Really resonates with me \<3

---

<div class="post-metadata">

**Author:** ![parallax](https://community.haxe.org/user_avatar/community.haxe.org/parallax/32/1726_2.png) [@parallax](https://community.haxe.org/u/parallax)\
**Post date:** [October 21, 2018, 12:40pm UTC](https://community.haxe.org/t/the-joy-of-haxe/1199/7 "2018-10-21T12:40:01Z")

</div>

Really nice article. It should be added to the haxe blog.

---

<div class="post-metadata">

**Author:** ![Fiene](https://community.haxe.org/user_avatar/community.haxe.org/fiene/32/724_2.png) [@Fiene](https://community.haxe.org/u/Fiene)\
**Post date:** [November 1, 2018, 12:07pm UTC](https://community.haxe.org/t/the-joy-of-haxe/1199/8 "2018-11-01T12:07:07Z")

</div>

I am a bit late to the party (but I clapped on Medium!!!) but I still want to say: Thank you so much for writing this! Not just because it is about Haxe, but also because I love your writing style. I Was chuckling and smiling throughout.

This was actually a really good article to show to some people I know who have no idea what Haxe is. They got it ^-^

---

<div class="post-metadata">

**Author:** ![meek](https://community.haxe.org/user_avatar/community.haxe.org/meek/32/471_2.png) [@meek](https://community.haxe.org/u/meek)\
**Post date:** [November 1, 2018, 4:32pm UTC](https://community.haxe.org/t/the-joy-of-haxe/1199/9 "2018-11-01T16:32:37Z")

</div>

Thanks. That’s nice to hear 😉

---

<div class="post-metadata">

**Author:** ![sundialservices](https://avatars.discourse-cdn.com/v2/letter/s/9e8a1a/32.png) [@sundialservices](https://community.haxe.org/u/sundialservices)\
**Post date:** [November 12, 2018, 1:04am UTC](https://community.haxe.org/t/the-joy-of-haxe/1199/10 "2018-11-12T01:04:30Z")

</div>

Yes, agreed, an excellent and well-written article.

The notion of _multi-platform_ development seems totally alien to so many people, yet it has saved my consultancy probably _tens of thousands of dollars(!)_ in development costs by credibly allowing us to develop on both the client and the server side at the same time. Furthermore, it lets us develop both “web-based client” software _and_ “mobile-app client” software – for multiple platforms(!) – **all** of the foregoing coming from a single code-base in a language with strong _compile-time_ error checking.

Nearly all of our projects originate from “rescuing” existing projects that have run into near-fatal trouble – umm, we’ve been doing that since 1992 – and _lately_ many of those were dying because “one project had blossomed into three, no make it four, no make it …” when **all** of those efforts were simply trying to work together to do the _one, same_ thing. In more than one occasion we **scrapped** several of these efforts in favor of Haxe. _(See footnote.)_.

We brought the project home _because of_ Haxe. (We owe a debt to its developers and to its community that we can never repay.) If we were to write a blog-post of our own experiences, it would read much like this one but undoubtedly be written much less well.

“Thanks for sharing.”

– – –  
_(Footnote)_ As it turns out, we were able to use OpenFL (in relevant cases) with apparently more success than this author did. _(Yay!)_ Of course, “every project is unique and different,” and … the sheer beauty and power of Haxe is that 'you can **choose**." You can even _un-make_ your decision – as the author did – without abandoning the entire benefits of the greater Haxe framework. _“And this, frankly, is revolutionary.”_
