The Zen of Haxe?

I came across this post in which a user condensed the “guiding principles” of Python into 19 aphorisms. I thought it would be interesting to see how the Haxe community would compose a similar list.

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren’t special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you’re Dutch.
Now is better than never.
Although never is often better than right now.
If the implementation is hard to explain, it’s a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea – let’s do more of those!

What would you folks write instead?

One language to rule them all,
one language to find them,
one language to bring them all,
and in the light bind them.


See zen of Haxe · Issue #9718 · HaxeFoundation/haxe · GitHub