Per-target score table

[markknol]

Maybe we should have a per-target score table somewhere. One column per target and then the rows are compilation time, run-time performance, native interop, debugging support and maybe more.

Like a feature matrix with checkmarks like (here)[https://haxe.org/foundation/support-plans.html] where 3 checkmarks = very good, no checkmarks = bad

We could take performance rates from the first graph at https://benchs.haxe.org/formatter-noio/

So python would be in the bad group, then eval + PHP in the next one, then C# and HL and JVM and Node, then C++ and Java. Neko isn't working, it's probably in the bad group too.

[Simn]

I like when my slack messages automatically turn into issues. :D