返回首页
最新
Hi HN,<p>This is a small RISC-V emulator I’ve been hacking on in Emacs Lisp as a fun weekend project.<p>It started mostly as a way to better understand the RISC-V spec by implementing things myself, and also as an excuse to write more non-trivial Emacs Lisp. It currently focuses on RV32I and related basics, and is very much not optimized or production-ready.<p>If you’re into RISC-V, emulators, or just enjoy seeing unusual things built in Emacs Lisp, feedback and comments are welcome<p>Happy hacking!
I’ve always struggled with traditional habit trackers. Filling out boxes every day feels robotic to me, and missing one day ruins the whole aesthetic.<p>So I built Voronoi just to use it myself. Instead of a rigid grid, it uses organic shapes to visualize your year. Your consistency paints a unique map associated with your time, rather than just checking off a list.<p>I've been using it for a while and it actually helps me stick to things, so I thought I'd share it here. I added a few other little tools and features that I personally needed along the way, but I'll let you discover those on your own.<p>Hope you find it useful.<p>https://getvoronoi.com
Hi HN, I made OSS Sustain Guard.<p>After every high-profile OSS incident, I wonder about the packages I rely on right now. I can skim issues/PRs and activity on GitHub, but that doesn’t scale when you have tens or hundreds of dependencies. I built this to surface sustainability signals (maintainer redundancy, activity trends, funding links, etc.) and create awareness. It’s meant to start a respectful conversation, not to judge projects. These are signals, not truth; everything is inferred from public data (internal mirrors/private work won’t show up).<p>Quick start:
pip install oss-sustain-guard
export GITHUB_TOKEN=...
os4g check<p>It uses GitHub GraphQL with local caching (no telemetry; token not uploaded/stored), and supports multiple ecosystems (Python/JS/Rust/Go/Java/etc.).<p>Repo: <a href="https://github.com/onukura/oss-sustain-guard" rel="nofollow">https://github.com/onukura/oss-sustain-guard</a><p>I’d love feedback on metric choices/thresholds and wording that stays respectful. If you have examples where these signals break down, please share.