|
|
|
|
|
|
by Gama11
2598 days ago
|
|
|
The "HashLink in-depth" blog post talks about this, an excerpt: > [...] Neko is very slow. The main reason for this is that it's dynamically typed. So every "value" in the VM can be either an Int, a Float, a Bool, some Bytes, an Array, a Function or Object, etc. And because this value needs to be recognized at run-time, its type together with its data need to be stored in the memory. [...] https://haxe.org/blog/hashlink-indepth/ |
|
|