Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I eventually decided to settle on programming the majority of my application in <strong>Lua</strong> using <a href="http://luajit.org/" rel="nofollow" title="LuaJIT">LuaJIT</a>, for a number of reasons, including:</p> <ul> <li>What I was trying to achieve through <strong>C/C++</strong> is already there in <strong>Lua</strong>, the hash tables and metafacilities specifically, and I was basically re-inventing the wheel.</li> <li>I did some simplistic benchmarking and discovered that most of my scripts would invariably end up bouncing calls to <strong>C</strong> and back to <strong>Lua</strong> very frequently, and that I could optimize away a lot of this by keeping the runtime focus limited to <strong>Lua</strong> by leveraging the bytecode compiler.</li> <li>From my limited experience and research on topics surrounding Just-in-Time compilation, <strong>LuaJIT</strong> (2.0.0-beta8) proves to be quite fast enough for my needs at this point and very possibly near to <strong>C++</strong> levels of memory usage for similar data structures.</li> <li><strong>LuaJIT</strong> also works excellently as a drop-in replacement for vanilla <strong>Lua</strong> and is easy to build; all I had to do was link to its library to get it up and running.</li> </ul> <p>I feel that I am losing a little of "power-user" control over my project by doing this, but I consider this to be due to my inexperience with the intricacies of <strong>Lua</strong> versus my knowledge of <strong>C++</strong>.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload