3 ms·
Since there is nothing obvious on the page: This is Lua+SQLite running on bare metal x86. Lots of questions: does it actually have any performance benefits? A
by nl 12y ago
Since there is nothing obvious on the page: This is Lua+SQLite running on bare metal x86.
Lots of questions: does it actually have any performance benefits? A network stack? How do the mechanics of getting/editing files work?
- hwh 12y agoThe codebase is so small that it's quite easy to take a look to answer the questions: * no networking at all * performance - doing what? * file primitives are implemented purely in Lua, and what is currently there resembles a pre-initialized ramfs. Closing a file is a NOP, the concept of numerical file descriptors is not fully implemented yet. So - no block devices yet. * aside from file primitives, you have lua coroutines as the core of the scheduling, inb()/outb() (bytewise port I/O), and putpixel/clearscreen in the API implemented in C, as well as basic keyboard handling (using inb/outb wrappers) and graphics primitives (using putpixel/clearscreen) implemented in Lua. I suggest to take a quick peek at luakernel.c and luakernel.lua in the codebase.
- justincormack 12y agoIf you want Lua running on bare metal with a network stack you can use the rump kernel[1]. [1] http://rumpkernel.org/ http://rumpkernel.org/
- vidarh 12y agoConsider this somewhat similar to booting up an 8-bit home-computer and get thrown into a BASIC prompt. It's a fun toy and a great experiment. It's not a "product". Play with it if you want to experiment with Lua and/or experiment with a simple OS built around a higher level language. Don't play with it if you want something to build your next app on.