🛠️ Hacker News Tools

[CLI Tool] Show HN: Attempt – A CLI for retrying fallible commands Hi HN,<p>Here&#x27;s a tool I wrote for retrying fallible commands. Nothing groundbreaking here, this is a tool that&#x27;s been made many times (and several have been submitted to Show HN). Though this one does have a more comprehensive feature set than most. I hope one or two people will find it useful.<p>I wrote `attempt` for two reasons:<p>- To have a more featureful alternative to `wait-for-it.sh` for use in Docker Compose. Specifically to apply migration scripts to a database that may not be up yet. I wanted to be able to inspect the error messages from my migration tool &amp; retry on connection errors.<p>- To test a hypothesis I had that a good way to make a CLI was to copy the API of a good library (in this case, `tenacity`). I want to write a blog post at some point to discuss this at length, but the tl;dr is that I believe it was a success.<p>Here are some usage examples: <a href="https:&#x2F;&#x2F;maxbondabe.github.io&#x2F;attempt&#x2F;usage.html" rel="nofollow">https:&#x2F;&#x2F;maxbondabe.github.io&#x2F;attempt&#x2F;usage.html</a><p>There may not be much to discuss for such a small tool, but I am open to all feedback and am happy to answer any questions.<p>Cheers,<p>Max

[Other] Using Emacs Org-Mode With Databases: A getting-started guide

[Other] Show HN: I made a simple ASCII-art analog clock in Emacs Just a toy, showing how easy it is to leverage built-in Emacs features (most notably Artist mode, which provides a set of functions for creating ASCII-art vector graphics) and things like trigonometric functions and timers to create something nice.<p>A short blog post mentioning some background (and showing a screenshot): <a href="https:&#x2F;&#x2F;mbork.pl&#x2F;2025-09-08_Emacs_Artist_clock#" rel="nofollow">https:&#x2F;&#x2F;mbork.pl&#x2F;2025-09-08_Emacs_Artist_clock#</a>.

[Other] NPM debug and chalk packages compromised <a href="https:&#x2F;&#x2F;github.com&#x2F;advisories&#x2F;GHSA-8mgj-vmr8-frr6" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;advisories&#x2F;GHSA-8mgj-vmr8-frr6</a>

[Other] Show HN: DevSwarm, run multiple AI coding assistants in parallel We wanted to run multiple AI coding assistants in parallel and swap models easily (Claude Code, local, Codex, etc.) without messing with the current branch.<p>DevSwarm is a mac&#x2F;windows desktop app that runs assistants on separate git branches so you can stay in the loop and compare&#x2F;merge safely. Not an IDE, an Augmented Development Environment (ADE); open any branch in your IDE with a click. We’ve been dogfooding it for months, including DevSwarm. Try it in minutes: download, open a repo, start two assistants. Free beta.

[Other] Logging in Go with Slog: A Practitioner's Guide

[Other] Go for Bash Programmers – Part II: CLI Tools

[Other] A clickable visual guide to the Rust type system

[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.