Is haxe alive or dead?

21

really .. the `popularity(what`all others is doing)
→ prevents you ?
~^
for me more counts whats stable run over time .)

22

Micha, 4sure .. the freedom of where you can get fall into a:
”fully experimental state” → can appear (^_^)
me often here ,. .,.,., into try to knot some existing “software” patterns together (from other targets^^)

23

Here is it :slight_smile: … in no specific order:

  • let to replace final var (immutable by default)
  • Int? as an alternative to Nullable<Int>
  • make function and var keywords optional when defining class members
  • public as the default visibility (I know this is quite debatable)
  • make new optional when instantiating classes (Enum already does this, why not classes?)
  • simplified getter/setter syntax (JS style)
  • optional semicolons (JS style)
  • optional parentheses for switch and maybe other constructs
  • proper JSX like syntax support
  • pipeline operator
  • nullish coalescing operator (not sure if this landed already)
  • optional chaining operator (not sure if this landed already)
  • simplified switch/case syntax (no case keyword at all :smiley: )
3 Likes
24

I still think Haxe is the bees knees. The design, to my mind, hits a sweet spot of complexity, and the fact it’s rooted with a proper macro system puts it ahead of anything.

Like, maybe if I were learning from scratch Haskell / Scala etc would tempt with JS implementations, but this grew up with a bunch of different considerations that mean that it’s set of features are small and principled.

I really like 5 so far, the code-completion is especially pleasing. It’s more tolerant and it’s snappy.

Coroutines are hard to implement so there’s been a hella work in the background to get that straight looks like.

my 2c

2 Likes
25

For an adjustment, there’s already ??/?. operators, optional switch parentheses and inline xml syntax with macro processing. There’s no final var, only final/var like const/let. New property syntax is also already decided, i think.

I agree that Int? would be a finishing touch for a nullsafety sugar instead of Null<Int>, probably most annoying thing to write for me (working on a codegen feature when typing ? char in a vshaxe tho).

Other things are nice too, but don’t bother me much personally, since there is @:publicFields class meta and missing field code generation. There’s also an autofix feature in vshaxe, that will fix missing semicolons on ctrl-s for lazy people like me :slight_smile:

2 Likes
26

for me the multiliterale free haxe language is at
L I V E
(not “dead” or such of things .. whats wrong with you ^~;:slight_smile:

tonight i am switched from string.Template
to pyra-engine (1200 lines lib only)

→ to TRANSPILE my H A X E ~^
t
m
p
l

( → catpi55/assets/haxeTMPL.hx at master · maitag/catpi55 · GitHub )

*hugs

(at first i am really get idea to transpile the haxe Template into Python ..
-._> a n y way → found that little pyralibCODE then \o/ → and no way out now.