Lua.vm.js

  • >Score: 130

    >binarytrees 46.051 seconds

    Without any frame of reference, those values are meaningless.

    However there is one I can evaluate:

    >1.58 MFLOPS

    Given I have an i7-2600 and its flops on benchmarks[1] (FPU Flops score: 8500.09 MFlops), that tells me something I could have guessed: performance is 3 orders of magnitude worse than native high performing code.

    Still, in order for this comparison to be complete, I'll have to

    - try this benchmark in Firefox with OdinMonkey, the new and very promising JS engine[2]

    - run a similar benchmark with "native" LUA

    edit: results obtained on W7 SP1 with 16GO RAM and Chrome 27.

    1: http://www.maxxpi.net/results/show.php?ID=c3x2c5w6d7b7

    2: did you know the logo was awesome? https://wiki.mozilla.org/File:Odinmonkey800.jpg

  • Would be interesting to compare performance to the other ways of getting Lua to run in the browser, which include writing a Lua bytecode interpreter in JS, converting Lua to JS, and code generation from bytecode.

    https://github.com/creationix/brozula https://github.com/mherkender/lua.js (and others, I had a list somewhere)

    Quite a few companies are using Lua->JS as a way of doing write once run cross platform games eg we had this talk at London Lua http://www.londonlua.org/luajavascript/index.html

  • I have no immediate use for this but goddamnit, it's cool.

  • Does anyone know of a good "compile to js" lua implementation ?

  • When people blog about don't use default bootstrap template, I often take it with a grain of salt. Now i'm absolutely positive.

  • <3 <3 <3