kernel-zig VS sectorlisp

Compare kernel-zig vs sectorlisp and see what are their differences.


:floppy_disk: hobby x86 kernel zig (by jzck)


Bootstrapping LISP in a Boot Sector (by jart)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
kernel-zig sectorlisp
2 25
412 1,166
- -
4.6 4.3
8 months ago 4 months ago
Zig C
- ISC License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of kernel-zig. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-10-31.


Posts with mentions or reviews of sectorlisp. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-02-26.
  • are there any benchmarks on sector lisp
    2 projects | /r/lisp | 26 Feb 2023
    I'm assuming you are referring to which I gather is an attempt to make a Lisp that fits in a disk boot sector?
  • Sectorlisp
    1 project | /r/hypeurls | 13 Jan 2023
    1 project | | 13 Jan 2023
  • Kilo Lisp: A Kilo Byte-Sized Lisp System
    11 projects | | 16 Dec 2022
  • For the LISP 1.5 mainframe fans here...
    4 projects | /r/mainframe | 15 Dec 2022
  • Ask HN: Best book to learn C in 2022?
    8 projects | | 8 Oct 2022
  • Take More Screenshots
    24 projects | | 24 Jul 2022
    I think SIMD was a distraction to our conversation, most code doesn't use it and in the future the length agnostic, flexible vectors; are a better solution. They are a lot like RVV;, research around vector processing is why RISC-V exists in the first place!

    I was trying to find the smallest Rust Wasm interpreters I could find, I should have read the source first, I only really use wasmtime, but this one looks very interesting, zero deps, zero unsafe.

    16.5kloc of Rust

    The most complete wasm env for small devices is wasm3

    20kloc of C

    I get what you are saying as to be so small that there isn't a place of bugs to hide.

    > “There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult.” CAR Hoare

    Even a 100 line program can't be guaranteed to be free of bugs. These programs need embedded tests to ensure that the layer below them is functioning as intended. They cannot and should not run open loop. Speaking of 300+ reimplementations, I am sure that RISC-V has already exceeded that. The smallest readable implementation is like 200 lines of code;

    I don't think Wasm suffers from the base extension issue you bring up. It will get larger, but 1.0 has the right algebraic properties to be useful forever. Wasm does require an environment, for archival purposes that environment should be written in Wasm, with api for instantiating more envs passed into the first env. There are two solutions to the Wasm generating and calling Wasm problem. First would be a trampoline, where one returns Wasm from the first Wasm program which is then re-instantiated by the outer env. The other would be to pass in the api to create new Wasm envs over existing memory buffers.


    MS-DOS, NES or C64 are useful for archival purposes because they are dead, frozen in time along with a large corpus of software. But there is a ton of complexity in implementing those systems with enough fidelity to run software.

    Lua, Typed Assembly; and Sector Lisp; seem to have the right minimalism and compactness for archival purposes. Maybe it is sectorlisp+rv32+wasm.

    If there are directions you would like Wasm to go, I really recommend attending the Wasm CG meetings.

    When it comes to an archival system, I'd like it to be able to run anything from an era, not just specially crafted binaries. I think Wasm meets that goal.

  • *Laughs in autocmd*
    4 projects | /r/neovim | 30 Jun 2022
    Based on this, the next thing you wrote, and your reference to running a minimal Gentoo: I think you might be a Scheme fan in the making. Scheme is the minimal Lisp. (Okay, that might be sectorlisp which fits in 512 bytes.) It’s hands down my favorite language. While it’s evolved on its own to be more of a superset of Scheme, Racket is my Scheme of choice.
  • Bootstrapping Lisp in a Boot Sector
    1 project | | 25 Jun 2022
  • That's pretty much it!
    7 projects | /r/ProgrammerHumor | 26 Feb 2022

What are some alternatives?

When comparing kernel-zig and sectorlisp you can also consider the following projects:

toaruos - A completely-from-scratch hobby operating system: bootloader, kernel, drivers, C library, and userspace including a composited graphical UI, dynamic linker, syntax-highlighting text editor, network stack, etc.

sectorforth - sectorforth is a 16-bit x86 Forth that fits in a 512-byte boot sector.

zap - An asynchronous runtime with a focus on performance and resource efficiency.

small-lisp - A very small lisp interpreter, that I may one day get working on my 8-bit AVR microcontroller.

zig-v8 - Simple V8 builds with C and Zig bindings.

Carp - A statically typed lisp, without a GC, for real-time applications.

zigup - Download and manage zig compilers.

mal - mal - Make a Lisp

gyro - A Zig package manager with an index, build runner, and build dependencies.

femtolisp - a lightweight, robust, scheme-like lisp implementation

minesweeper-zig - Simple Minesweeper clone written in Zig, using SDL for graphics.

wisp - A little Clojure-like LISP in JavaScript