axiom-zig VS mummy

Nim is also a strong player as a systems programming language. In terms of memory management, it's configurable, and by default you get ARC (no GC). I've written a hobby kernel (if you can call it that) in Nim[1] as well as Zig[2], and I found Nim to be much more ergonomic and approachable. The fact that Zig requires weaving an allocator through most calls that may allocate gets in the way of what I'm trying to do. I'd rather focus on core logic and have ref counting take care of dropping memory when appropriate.

One thing I wish Nim had though is true sum types with payloads. I think there's an RFC for that, but it's a shame it's not in the language yet.

[1] https://github.com/khaledh/axiom

[2] https://github.com/khaledh/axiom-zig

If anyone is interested, I have a couple of implementations of booting under UEFI and getting a bunch of info about the system (don't expect a functioning system, they just boot and dump some info):

Nim: https://github.com/khaledh/axiom

Zig: https://github.com/khaledh/axiom-zig (this one goes into depth in disassembling ACPI DSDT bytecode)

Personally this preciseness is just a distraction, but it sounds like you have learned from the constraints and can now take the training wheels off again.

Very curious about those cases, yet to find one myself that was not because of a bad design decision. Though I am also very big on the idea of `ambiguous grammar, rigorous implementation`, for natural language too. (Toki Pona is a somewhat extreme example but the contextual grammar, and holistic minimalism is fascinating)

Not to make it longer than needs to be; But take the example code in this readme: https://github.com/guzba/mummy

Being able to quickly script this without thinking about cases or style on the first pass is a really lovely way of reducing friction imho.

Added a WebSocket chat example here: https://github.com/guzba/mummy/blob/master/examples/chat.nim