PHP vs Haxe

According to the 2015 Stack Overflow Developer Survey (26,086 people surveyed), PHP was the 5th most popular/used language at 29.7%.

Many clients are looking for an easy-to-update web site that's flexible and free. Drupal and Wordpress fill those needs very well.

Part of the de facto standard web application stack.

PHP standard library is somewhat subpar, but if you need plugins, language features, composer has them all( you can even puzzle together a custom framework from composer).

Since 7.x was released, PHP has become a pretty fast language.

PHP people love frameworks, and with frameworks such as Laravel, you can build a web app or API really fast (Facades, ORMs, scaffolding etc.)

Haxe allows you to develop for Web, iOS, Android, Blackberry, Windows, OSX, Linux and others, all at once, without the need to switch languages and maintain separate code bases.

This is possible because Haxe can compile to JavaScript, ActionScript, Flash AVM bytecode, C++, Neko, PHP, C# (.NET) and Java.

Support for even more platforms and languages is under development.

The language was designed to be very expressive with the smallest possible amount of syntactic sugar. There are actually fewer keywords than other languages with similar power.

Haxe can easily compile over 100,000 lines of code to JS in seconds on a mid-spec computer.

One big advantage over pure javascript, (or some other languages listed here) is that Haxe will pick up a whole range of errors when you compile, saving you the pain of having to try and debug them later. This includes everything from syntax errors ("Unexpected ;") to type errors ("Class user has no field username. Suggestion: username").

Haxe has the ability to use "externs". These are haxe files which describe the usage of existing JS libraries. Get code completion and compile-time-checking for everything from jQuery to Node.js.

Even without externs, native JS code can still be used through untyped code.

Code completion is built into the compiler and available to the IDE allowing for much smarter code completion that can actually parse and understand the syntax tree.

Syntactic macros allow you to extend compiler features at the syntax tree step. Macros come into play after code is parsed into the abstract syntax tree, and macros allow you to transform it before the rest of the compilation completes.

This provides for immense power, while at the same time scoping the extensibility at a level that is powerful, but well constrained.

Haxelib (common library repo) and other sources contain large codebases for anything from cryptography to communications. A lot of these are fully cross platform and work with the JavaScript target.

The JavaScript target can be used for everything from node.js server applications (with code completion) to games using either the Flash-like OpenFL library or direct canvas or WebGL programming.

You can use the same classes on the server as you do on the client where applicable. This saves a lot of time.

The language is very easy to learn for those with background in JavaScript or ActionScript 3.

The output that is generated can be trimmed using "dead code elimination" to only include those functions and libraries that are strictly necessary. All code is very readable with only minimal extras for specific functionality.

Small output is good for frontend development as file size is a major concern.

Haxe has been around for more than 10 years (since 2005) and whilst not the most popular project, has had continuous growth.

Highly unlikely to disappear or for support to stop.

After a type is inferred from its context, it cannot be changed to a new type, and type safety is done at compile time so it stays safe without the extra maintenance required for static typing.

Friendly community

Using a remoting proxy you can get type safe server to client communications, allowing for remote method execution on the server as if they were part of the client side code.

Package tree is just directory tree, it's wonderful!

Haxe supports conditional compilation, so depending on compiler flags Haxe will include or exlcude sections of your code. Making it easy to have debug and release builds.

Haxe compiler will check types when using externs for existing libraries.

Haxe has the power and expression to not need the npm dependancy hell that is common in js and typescript, bit it's still simple.

You can define constants in an abstract enum and when used in a switch/case statement Haxe checks for exhaustiveness, making sure every constant is covered - with no runtime implication.

You should use externs when calling non Haxe code, but if you just need to call one or two external JS functions, you can skip type checking by calling untyped code.