Show HN: Let – Offline-first life events tracker (React Native, SQLite) https://ift.tt/to16GL9

Show HN: Let – Offline-first life events tracker (React Native, SQLite) https://ift.tt/eZbMtU1 May 4, 2026 at 03:53AM

Show HN: I built my site as a Windows 95 experience (2025) https://ift.tt/FUjN6AW

Show HN: I built my site as a Windows 95 experience (2025) Have fun with the disk defragmenter. https://wes.dev/ May 3, 2026 at 02:30AM

Show HN: I built a RISC-V emulator that runs DOOM https://ift.tt/m8Z7Ojs

Show HN: I built a RISC-V emulator that runs DOOM Hi HN, I built a RISC-V emulator that implements the RV32IM instruction set and a minimal syscall interface to run DOOM. A few weeks ago, I got my first output with a simple hello world assembly program. Since then I have been working tirelessly to get DOOM to run. I needed to figure out how to run C programs first, and came across newlib, which allows the underlying environment to implement the syscall stubs one by one until the programs run. I have also added ELF loading, but currently only a single `PT_LOAD` segment is supported. To port DOOM, I used doomgeneric, which was quite convenient to get working once the required stubs were in place. DOOM renders to a fixed area in memory (0x705FDD = VRAM_START): 0x7FFFFF +-------------------------------------+ | | | QUEUE_SIZE (32 bytes) | | | 0x7FFFDF +-------------------------------------+ <-- QUEUE_START 0x7FFFDE | QUEUE_READ_IDX | 0x7FFFDD | QUEUE_WRITE_IDX | +-------------------------------------+ | | | | | VRAM (1,024,000 bytes) | | | | | 0x705FDD +-------------------------------------+ <-- STACK_START | Stack | | | | | v | | | | ^ | | | | | Program data + Heap | | | 0x000000 +-------------------------------------+ I made a small linker script so that the entry point of a C program is at _start and virtual address is always 0. That kept the ELF loader code simple. Inputs are written to the queue by rvcore which are then intercepted by DOOM running inside it. Demo link: https://www.youtube.com/watch?v=f5uygzEmdLw https://github.com/lalitshankarch/rvcore May 3, 2026 at 01:57AM

Show HN: Apple's Sharp Running in the Browser via ONNX Runtime Web https://ift.tt/Xy3mfJQ

Show HN: Apple's Sharp Running in the Browser via ONNX Runtime Web https://ift.tt/ZrRMu8s May 2, 2026 at 11:14PM

Show HN: DAC – open-source dashboard as code tool for agents and humans https://ift.tt/5Jz8Ul3

Show HN: DAC – open-source dashboard as code tool for agents and humans Hi all, this is Burak. When agents became a reality one of the first things I wanted to do was to automate building dashboards. The first, and the most obvious, wall that I ran into was that a lot of the tools were just driven by UI. This meant that without the agents handling browser UIs and whatnot, it wasn't possible to have the agents do that. In addition, it would be impossible to review any of the changes the agent would make. The first instinct there is to get your agent to build a React app for the dashboard. This works beautifully for the happy path, but I quickly ran into other issues there: - every dashboard turns out to be different - have to implement a backend to centralize the query execution - there is no centralized mechanism to control the rules and standards around visualizations - there is no way to get a semantic layer working with the dashboards easily In the end, agents ended up reinventing the wheel for every new dashboard, even under the same project. Building a standardized, local project for these turned out to be building a BI tool from scratch. After trying these out, I asked myself: what if the dashboards were built for agents as the primary user? A product like that would need to have a couple of features: - First of all, everything needs to be driven by version-controllable text. YAML is fine. - Changes to the dashboards should be easy to review and understand by humans. - Agents are great at writing code, it'd be great if this were driven by code to have dynamic stuff: JSX would be great. - Static analysis being a first-class citizen: validate dashboards before deploying. Agents can check their work too. - A standardized way of deploying these based on a couple of files in a folder: operationally very simple. - Built-in semantic layer to standardize metrics. That's what I ended up building: dac (Dashboard-As-Code) is an open-source tool and a spec to define dashboards, well, as code. It contains an implementation in Go that can be deployed as a single binary anywhere. The dashboards are defined in YAML and JSX, YAML for static stuff, JSX for dynamic dashboards. You can run queries at load time to define conditional charts, generate tabs on the fly per customer, or list charts for each A/B test you are running. I built it in Go because I do love Go, and I think it is the greatest language at the moment to work with AI agents. dac runs as a single binary, you can get started with a `dac init` command and it'll automatically create some sample dashboards for you based on duckdb. It supports 10+ SQL backends, with more to come. It supports validation, custom themes and whatnot. You can see it here: https://ift.tt/JGEcU9I I would love to hear what can be improved here, please let me know your thoughts. https://ift.tt/JGEcU9I April 29, 2026 at 04:37AM

Show HN: I built a context layer for our home https://ift.tt/0AbqXN5

Show HN: I built a context layer for our home Rosey started as a grocery list. My wife and I kept losing track of which phone the list was on. So I built a number we could both text, a shared little assistant that just remembered. Once it remembered groceries, it was a small step to remembering the wifi password, the pediatrician's number, what we usually buy at our grocery store, what the plumber said. From there, the obvious idea: this is the household's context layer, the thing that knows the shared facts so neither person has to be the one who remembers. https://rosey.house April 30, 2026 at 08:15PM

Show HN: WhatCable, a tiny menu bar app for inspecting USB-C cables https://ift.tt/7Aepk0P

Show HN: WhatCable, a tiny menu bar app for inspecting USB-C cables USB-C cables can be a mess. One cable charges at 5W, another does 100W and Thunderbolt 4, and they look identical in the drawer. WhatCable sits in your menu bar and reads the cable data your Mac already has access to. Plug in a cable and it tells you in plain English what it can actually do: charging wattage, data speed, display support, Thunderbolt, etc. Built in Swift/SwiftUI. Open source, free, no tracking. GitHub: https://ift.tt/E9yRBUP https://ift.tt/E9yRBUP April 30, 2026 at 10:43PM