Haxe 4.0.0 preview 2: final keyword, arrow functions

I tend to feel that not being backed by a large corporation is a point in Haxe's favour.

It's making the argument that it should be used because it is good. Improvements to the language have to stand on their own merit rather than what would drive the parent coproration's agenda.

IIRC, you can use either. Whatever quote you used to start the string is the one that will end the string.

var foo:String = "foo"; // foo

var bar:String = 'bar'; // bar

var fooquotebar:String = "foo'bar"; // foo'bar

Shell and basically every other language that makes that distinction (PHP, Ruby, Perl...).

This is pretty annoying, but you get used to it. After so long it would be a major pain to break everyone's strings by flipping the syntax.

They probably started with quoted string literals (same syntax as ActionScript, I think, plus many other languages of course), then added string interpolation later and realised they needed a different syntax for it.

(Another option: they looked at what the POSIX-style shell does, and did exactly the opposite. And as language design strategies go, that is far from the worst possible.)

Do you mean Neko https://en.wikipedia.org/wiki/Neko_(programming_language)? Haxe itself compiles into another language(https://haxe.org/manual/compiler-usage.html) that would run on the server.

There are several ways to do it: compile to C++, compile to the Neko VM, or use Node (there are official bindings: https://github.com/HaxeFoundation/hxnodejs) In development it's Haxe (which is a lovely language to work with) but in production it can be something you're familiar with.

Haxelib (the Haxe package manager) client and server are both written in Haxe. Also try.haxe.org and kodegarden.org clients+servers are also written in Haxe.