unzig
tigerbeetle
unzig | tigerbeetle | |
---|---|---|
6 | 46 | |
11 | 7,263 | |
- | 8.4% | |
0.0 | 9.9 | |
about 1 year ago | 4 days ago | |
Zig | Zig | |
MIT License | Apache License 2.0 |
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.
unzig
- Show HN: Zig Without Unused Variable Errors
-
Added a flag to remove unused variable error
I really like Zig but the unused variable error really gets in the way of how I usually do exploratory code. I've managed to produce a forked version from release 0.10.1 that adds an --allow-unused flag which disables the error. The code is hacky but it seems to work. I didn't understand a lot about Zig's caching mechanism so I might have been a little aggressive in invalidating caches when the flag is switched on and off.
-
What “sucks” about Zig?
I originally pulled it from here: https://github.com/markisus/unzig
-
Zig: The Modern Alternative to C
It already exists. You’ll just have to compile it yourself which is relatively easy.
https://github.com/markisus/unzig
- Show HN: Zig Without Unused Variable Error
-
Compiling Zig with Low RAM (16GB)?
I predict / hope that in the future, the community will just host patched binaries somewhere, but for now I have gone ahead and created a patch repo whose sole purpose is to remove the unused variable error where you still have to rebuild from source. https://github.com/markisus/unzig
tigerbeetle
-
Redis Re-Implemented with SQLite
I'm waiting for someone to implement the Redis API by swapping out the state machine in TigerBeetle (which was built modularly such that the state machine can be swapped out).
https://tigerbeetle.com/
-
The Fastest and Safest Database [video]
I fully agree with what Prime says at the end - Joran has really set a new bar here for all future database presentations.
Hearing that the entire TigerBeetle domain logic lives in a single file [0] (and is intended to be pluggable for other OLTP use cases!) makes it 1000% more tempting to spend the weekend getting up to speed with Zig.
[0] https://github.com/tigerbeetle/tigerbeetle/blob/main/src/sta...
-
Building a Scalable Accounting Ledger
Why would you want to build your own accounting ledger from scratch? Accounting is a completely new domain for most engineers, and TigerBeetle (https://tigerbeetle.com/) already solves this problem.
- Tiger Style
- Tigerbeetle's Storage Fault Model
- Factor is faster than Zig
-
The Raft Consensus Algorithm
Maelstrom [1], a workbench for learning distributed systems from the creator of Jepsen, includes a simple (model-checked) implementation of Raft and an excellent tutorial on implementing it.
Raft is a simple algorithm, but as others have noted, the original paper includes many correctness details often brushed over in toy implementations. Furthermore, the fallibility of real-world hardware (handling memory/disk corruption and grey failures), the requirements of real-world systems with tight latency SLAs, and a need for things like flexible quorum/dynamic cluster membership make implementing it for production a long and daunting task. The commit history of etcd and hashicorp/raft, likely the two most battle-tested open source implementations of raft that still surface correctness bugs on the regular tell you all you need to know.
The tigerbeetle team talks in detail about the real-world aspects of distributed systems on imperfect hardware/non-abstracted system models, and why they chose viewstamp replication, which predates Paxos but looks more like Raft.
[1]: https://github.com/jepsen-io/maelstrom/
[2]: https://github.com/tigerbeetle/tigerbeetle/blob/main/docs/DE...
- Fastest Branchless Binary Search
-
CWE Top Most Dangerous Software Weaknesses
> There is no reason to use a memory unsafe language anymore, except legacy codebases, and that is also slowly but surely diminishing. I'm still yet to hear this amazingly compelling reason that you just need memory unsafe languages. In terms of cost/benefits analysis, memory unsafety is literally all costs.
Tell that to the authors of new memory unsafe languages (like Zig) and creators of new project in those languages (like https://tigerbeetle.com) :(
- Problems of C, and how Zig addresses them
What are some alternatives?
libxev - libxev is a cross-platform, high-performance event loop that provides abstractions for non-blocking IO, timers, events, and more and works on Linux (io_uring or epoll), macOS (kqueue), and Wasm + WASI. Available as both a Zig and C API.
LevelDB - LevelDB is a fast key-value storage library written at Google that provides an ordered mapping from string keys to string values.
bitcoin-bash-tools - Set of bitcoin-related bash functions
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
aviary.sh - Minimal distributed configuration management in bash
bun - Incredibly fast JavaScript runtime, bundler, test runner, and package manager – all in one
bash2048 - Bash implementation of 2048 game
reshade - A generic post-processing injector for games and video software.
v - Simple, fast, safe, compiled language for developing maintainable software. Compiles itself in <1s with zero library dependencies. Supports automatic C => V translation. https://vlang.io
rafiki - An open-source, comprehensive Interledger service for wallet providers, enabling them to provide Interledger functionality to their users.
Box2D - Box2D is a 2D physics engine for games