🛠️ Hacker News Tools

[Other] ApeRAG: Production-ready GraphRAG with multi-modal indexing and K8s deployment

[Other] Immich – High performance self-hosted photo and video management solution

[Other] Show HN: C++ Compiler Support Page Hi HN,<p>I have created a webpage that displays all C++ features since C++20 in a simple, searchable table.<p>It is intended to serve as a quick reference for C++ developers, whether as support for cross-platform development or simply to track the current support status out of curiosity.<p>I created it as a simpler, more structured, and more up-to-date alternative to the cppreference compiler support site. Please note that the page intentionally does not list LWG and CWG papers. This might change as I am continually updating the site and trying out new ideas.<p>Questions, feedback and suggestions are appreciated, either here or in the form of GitHub issues.

[Other] Using Claude Code to modernize a 25-year-old kernel driver

[Other] Taking Buildkite from a side project to a global company

[Other] Pico CSS – Minimal CSS Framework for Semantic HTML

[CLI Tool] Show HN: Psq – CLI for Postgres Monitoring

[CLI Tool] Show HN: GitType – A typing game that uses your own Git repo as practice text I built a small Rust CLI game called GitType.<p>It’s a typing practice tool that takes <i>your own Git repository</i> and turns the code inside into typing material. Instead of random words, you type through real functions, comments, and code you’ve written — making practice feel closer to real-world programming.<p>Features: - Works directly in the terminal (no GUI required) - Pulls text from any local Git repo - Tracks WPM and accuracy - Keeps a history of your past runs (so you can see progress over time) - Fun ranking titles based on your score<p>Source and install instructions: <a href="https:&#x2F;&#x2F;github.com&#x2F;unhappychoice&#x2F;gittype" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;unhappychoice&#x2F;gittype</a><p>Would love feedback from fellow devs — especially around the scoring system and ideas for new modes. :)

[Testing] Show HN: Vizzly – Visual testing platform with built-in review workflows Hey HN! I’m Robert. I worked on [Percy’s SDKs&#x2F;support from 2018–2022.](<a href="https:&#x2F;&#x2F;github.com&#x2F;percy&#x2F;cli&#x2F;graphs&#x2F;contributors" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;percy&#x2F;cli&#x2F;graphs&#x2F;contributors</a>) If you ever reached out to support or opened an issue, I probably helped you. Hopefully it was positive :) After a few years away, visual testing still felt stuck, so I&#x27;m building Vizzly.<p>The problem: Design handoffs kinda suck. Designers make beautiful specs, devs implement them, then everyone realizes the details got lost somewhere. Current visual testing tools catch broken CSS but miss the real issue - making sure what ships actually matches what was designed, functionally (like really in the browser&#x2F;OS&#x2F;etc).<p>What it is<p>- Visual testing + review where you send actual screenshots (not DOM re-renders). Can be _any_ image to review (PDFS!)<p>- Collaboration built-in: reviewer assignment, approvals, @mentions, screenshot-level threads.<p>- Baselines: automatic (Git-aware), manual (not Git-based), or hybrid.<p>- Team-based pricing; generous free plan for OSS; on-prem available.<p>What’s different<p>- Capture-first: use the pixels your app produced (no “but it doesn’t look like that on my machine&#x2F;CI”).<p>- Local TDD + CI parity: run locally with instant feedback; same flow in CI.<p>- Custom properties to filter&#x2F;slice reviews (component, viewport, theme, etc).<p>Try it quickly (Playwright example)<p>```<p>npm i -D @vizzly-testing&#x2F;cli<p>export VIZZLY_TOKEN=your-token<p># in your tests:<p>import { vizzlyScreenshot } from &#x27;@vizzly-testing&#x2F;cli&#x27;;<p>let img = await page.screenshot({ fullPage: true });<p>await vizzlyScreenshot(&#x27;homepage-layout&#x27;, img);<p>```<p>I would love feedback on everything! Rough edges you hit using the product&#x2F;sdk, baseline expectations across branches, what you need for design&#x2F;dev review to feel “done”, etc. Features like root cause analysis, an MCP, and more collab features are coming. But it&#x27;s just me building :p<p>I&#x27;m a big fan of OSS, so the OSS plan is pretty generous (10 seats + 10 review seats (20 total), unlimited public projects, 75GB, 6 concurrent builds). If it&#x27;s not generous enough for teams, I&#x27;m willing to up it!<p>This is my first time launching anything like this, I&#x27;m super keen on getting feedback and working any support or suggestions folks have. If anyone knew me from my support at Percy, I _really_ enjoy those conversations and opportunities to ship a fix or feature at the end of a chat. If Vizzly isn&#x27;t it for your team, I wanna know why and what I can do to help you.<p>Backstory + screenshots from my intro blog post: <a href="https:&#x2F;&#x2F;robertdelu.ca&#x2F;2025&#x2F;09&#x2F;07&#x2F;vizzly-introduction" rel="nofollow">https:&#x2F;&#x2F;robertdelu.ca&#x2F;2025&#x2F;09&#x2F;07&#x2F;vizzly-introduction</a>

[Other] Show HN: Bottlefire – Build single-executable microVMs from Docker images

[Other] Show HN: Semantic grep for Claude Code (RUST) (local embeddings)

[Other] Show HN: An Open Source XR(AR/VR) Operating System We&#x27;re two college students building an XR(AR&#x2F;VR) native Operating System with a custom kernel. We&#x27;re also Open Source so feel free to check our GitHub Repository- <a href="https:&#x2F;&#x2F;github.com&#x2F;manaskamal&#x2F;XenevaOS" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;manaskamal&#x2F;XenevaOS</a> .<p>The journey hasn&#x27;t exactly been easy, we&#x27;ve been criticized by a lot saying that whatever we&#x27;re doing is impractical and that we&#x27;re too ambitious. Regardless, we&#x27;ve been committed to reach our goal.<p>Here to answer all questions and doubts. Answering one question beforehand because we know someone is going to ask it -<p>Q: Why use your own kernel&#x2F; Why don&#x27;t you use Linux&#x2F; Why are you trying to reinvent the wheel?<p>A: Using our own kernel helps us get rid of the baggage of legacy codes, bring the most optimal performance on our target hardware (XR&#x2F;AR&#x2F;VR) and achieve more efficiency than what we would&#x27;ve achieved on an existing kernel.<p>We&#x27;re not trying to reinvent the wheel, but just building Formula One racing tyres for it.

[Other] Show HN: I'm a dermatologist and I vibe coded a skin cancer learning app Coded using Gemini Pro 2.5 (free version) in about 2-3 hours.<p>Single file including all html&#x2F;js&#x2F;css, Vanilla JS, no backend, scores persisted with localStorage.<p>Deployed using ubuntu&#x2F;apache2&#x2F;python&#x2F;flask on a £5 Digital Ocean server (but could have been hosted on a static hosting provider as it&#x27;s just a single page with no backend).<p>Images &#x2F; metadata stored in an AWS S3 bucket.

[Other] Things you can do with a debugger but not with print debugging

[API/SDK] Show HN: CrabCamera – Cross-platform camera plugin for Tauri desktop apps After building several Tauri desktop apps, I kept hitting the same wall: there&#x27;s no reliable way to access cameras across Windows, macOS, and Linux. Every project meant reinventing camera integration, dealing with platform-specific APIs, and debugging permission issues.<p><pre><code> So I built CrabCamera – a Tauri plugin that handles all the camera complexity for you. What it does: - One API, three platforms: Same Rust code works on Windows (DirectShow), macOS (AVFoundation), and Linux (V4L2) - Permission handling: Automatically requests camera permissions on each platform - Format conversion: Takes care of the messy bits between platform formats and what your app needs - Error handling: Proper Rust error types instead of mysterious crashes - Hot-plugging: Detects when cameras are connected&#x2F;disconnected The problem it solves: Before CrabCamera, adding camera support to a Tauri app meant: 1. Writing separate native code for each platform 2. Managing three different permission systems 3. Handling format conversions manually 4. Debugging platform-specific edge cases 5. Maintaining it all as OS APIs change Now it&#x27;s just: use crabcamera::Camera; let camera = Camera::new()?; let frame = camera.capture_frame().await?; Why I built it: I was working on a plant monitoring app (botanica) that needed reliable camera access for time-lapse photography. Existing solutions were either abandoned, platform-specific, or required complex native bindings. The Tauri ecosystem is growing fast, but camera support was this obvious gap. Every desktop app eventually needs camera access – video calls, document scanning, AR features, security monitoring. Technical highlights: - Uses nokhwa for the heavy lifting but wraps it in Tauri-friendly APIs - Proper async&#x2F;await support throughout - Memory-efficient streaming for video capture - Built-in image processing pipeline - Extensible plugin architecture What&#x27;s next: - WebRTC integration for video calls - Built-in barcode&#x2F;QR code scanning - Face detection hooks - Performance optimizations for 4K streams The crate is MIT licensed and available on crates.io. I&#x27;d love feedback from other Tauri developers who&#x27;ve wrestled with camera integration. Links: - Crates.io: https:&#x2F;&#x2F;crates.io&#x2F;crates&#x2F;crabcamera - GitHub: https:&#x2F;&#x2F;github.com&#x2F;Michael-A-Kuykendall&#x2F;crabcamera - Documentation: https:&#x2F;&#x2F;docs.rs&#x2F;crabcamera</code></pre>

[Other] Longhorn – A Kubernetes-Native Filesystem

[Other] Show HN: Lightweight tool for managing Linux virtual machines hey guys. the other day i was migrating hosting providers and i just needed something not too heavy and convenient to spin up my backups for awhile and realised there is almost nothing out there. kimchi hasn&#x27;t been updated for years and cockpit is heavy. so here&#x27;s something i came up with in a couple hours because of a sudden urge, nothing fancy just basic creation with cloud init, lifecycle management and image&#x2F;storage, but it&#x27;s modern-ish and it compiles to a 8.4mb binary inclusive of the embedded web UI, CLI and API, and only dep is libvirt.

[CLI Tool] Show HN: Greppers – fast CLI cheat sheet with instant copy and shareable search I kept re-Googling the same flags, so I built a tiny, fast directory of copy-ready CLI commands. It’s static (vanilla JS), instant search, keyboard nav (↑&#x2F;↓ + Enter), favorites (localStorage), and linkable queries.<p>Examples: • grep errors → <a href="https:&#x2F;&#x2F;www.greppers.com&#x2F;?q=grep%20error%20logs" rel="nofollow">https:&#x2F;&#x2F;www.greppers.com&#x2F;?q=grep%20error%20logs</a> • list open ports (macOS) → <a href="https:&#x2F;&#x2F;www.greppers.com&#x2F;?q=list%20open%20ports" rel="nofollow">https:&#x2F;&#x2F;www.greppers.com&#x2F;?q=list%20open%20ports</a> • show git branch graph → <a href="https:&#x2F;&#x2F;www.greppers.com&#x2F;?q=git%20graph" rel="nofollow">https:&#x2F;&#x2F;www.greppers.com&#x2F;?q=git%20graph</a> • tail with colors → <a href="https:&#x2F;&#x2F;www.greppers.com&#x2F;?q=tail%20colors" rel="nofollow">https:&#x2F;&#x2F;www.greppers.com&#x2F;?q=tail%20colors</a><p>Suggest a missing command: <a href="https:&#x2F;&#x2F;www.greppers.com&#x2F;submit.html" rel="nofollow">https:&#x2F;&#x2F;www.greppers.com&#x2F;submit.html</a><p>I’m looking for gaps and better real-world examples. Feedback welcome.

[Other] Show HN: Find the cheapest protein per gram across 3000 powders I tracked protein powder prices in a spreadsheet for years and found that identical protein content can have wild price differences.<p>I built PricePerProtein to automate it. It pulls real-time Amazon data (Keepa API) and uses Gemini 2.5 Flash to extract nutrition facts from product images&#x2F;descriptions. Calculates actual protein per dollar, not just package price.<p>Technical: FastAPI + Celery backend, Next.js frontend with virtual scrolling to handle 3000+ products. Deployed on a VPS (migrated from GCP - much simpler). The AI handles everything from blurry nutrition labels to understanding flavor categories.<p>No signup, no ads, no affiliate links. Updates hourly.

[Other] Stop writing CLI validation. Parse it right the first time