🛠️ Hacker News Tools

[Other] Show HN: Bolt – A super-fast, statically-typed scripting language written in C I&#x27;ve built many interpreters over the years, and Bolt represents my attempt at building the scripting language I always wanted. This is the first public release, 0.1.0!<p>I&#x27;ve felt like most embedded languages have been moving towards safety and typing over years, with things like Python type hints, the explosive popularity of typescript, and even typing in Luau, which powers one of the largest scripted evironments in the world.<p>Bolt attempts to harness this directly in the lagnauge rather than as a preprocessing step, and reap benefits in terms of both safety and performance.<p>I intend to be publishing toys and examples of applications embedding Bolt over the coming few weeks, but be sure to check out the examples and the programming guide in the repo if you&#x27;re interested!

[Other] Flintlock – Create and manage the lifecycle of MicroVMs, backed by containerd

[Other] Show HN: Engineering.fyi – Search across tech engineering blogs in one place I built a search engine for engineering blogs because I was tired of manually checking individual company blogs to find real-world production examples.<p>The problem: When learning a new technology, the best insights often come from how companies like Google, Meta, or Stripe actually implement it in production. But these gems are scattered across dozens of separate engineering blogs with no way to search across them.<p>What I built: Engineering.fyi indexes engineering blogs from ~15 companies (Google, Meta, OpenAI, Anthropic, Stripe, Uber, etc.) and makes them searchable in one place. You can filter by topic, difficulty level, and whether articles include code samples.<p>Technical details: - Built with Next.js, SQLite, DrizzleORM - Custom scrapers for each blog (they&#x27;re all frustratingly different) - Basic tagging system using content matching (still improving this)<p>Current status: Core search is working. Adding new blogs weekly as I index them.<p>Next features (based on early feedback): - AI summaries for quick article previews - Weekly digest of trending engineering insights - Save&#x2F;bookmark articles (considering whether to add accounts)<p>Interesting challenges: - Each blog requires custom parsing logic (no standard format) - Building an accurate tagging system is harder than expected – started with exact matching but exploring better approaches<p>I&#x27;d love feedback on: - Which company engineering blogs you&#x27;d find most valuable to include - Whether AI summaries would actually be useful or just noise - How you currently discover engineering articles from these companies

[Other] POML: Prompt Orchestration Markup Language

[Other] Ch.at – a lightweight LLM chat service accessible through HTTP, SSH, DNS and API

[Other] An AI-first program synthesis framework built around a new programming language

[Other] ESP32 Bus Pirate 0.5 – A hardware hacking tool that speaks every protocol ESP32 Bus Pirate is an open-source firmware that turns your device into a multi-protocol hacker&#x27;s tool, inspired by the legendary Bus Pirate.<p>It supports sniffing, sending, scripting, and interacting with various digital protocols (I2C, UART, 1-Wire, SPI, etc.) via a serial terminal or web-based CLI.<p>Modes for:<p>- HiZ (default) - I2C (scan, glitch, slave mode, dump) - SPI (flash, sdcard, slave mode) - UART &#x2F; Half-Duplex UART (bridge, read, write) - 1-WIRE (ibutton, temp sensor) - 2WIRE (smartcard) &#x2F; 3WIRE (eeprom) - DIO (Digital I&#x2F;O, read, pullup, set) - Infrared (device-b-gone, send and receive) - USB (HID, mouse, keyboard, gamepad, storage) - Bluetooth (BLE HID, scan, spoofing, sniffing) - Wi-Fi (scan, AP, connect, sniff, deauth) - JTAG (scan pinout, SWD) - LED control (animations, set LEDs) - I2S - CAN<p><a href="https:&#x2F;&#x2F;github.com&#x2F;geo-tp&#x2F;ESP32-Bus-Pirate" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;geo-tp&#x2F;ESP32-Bus-Pirate</a>

[Other] How to safely escape JSON inside HTML SCRIPT elements

[Other] Build durable workflows with Postgres

[IDE/Editor] Efrit: A native elisp coding agent running in Emacs

[Other] Show HN: Selfhostllm.org – Plan GPU capacity for self-hosting LLMs A simple calculator that estimates how many concurrent requests your GPU can handle for a given LLM, with shareable results.

[Code Quality] Byte Buddy is a code generation and manipulation library for Java

[Other] Show HN: BaaS to build agents as data, not code Agents and workflows as data instead of code.<p>Julep is a backend-as-a-service to build agents and workflows. Main features:<p>1. Experimentation Velocity:<p>With most agent frameworks, agents are code that need to be deployed. To iterate on the prompts or update the agent, you need to make changes to the code and deploy it to your server. This makes agents hard to iterate on quickly. But with agents and tasks declared as data, all that happens in the background is make an api call to update or make a new entry in the database. This increases the experimentation velocity.<p>2. Scalability and long-running background tasks:<p>Scaling is a hard software engineering problem and the solution is to define large scale systems to be distributed, stateful and scalable. Agents as data is a very helpful paradigm because you have to solve for this problem only once at the orchestrator level. Julep can handle 100s of thousands of executions paralely.<p>3. Updating an agent &#x2F; User Personalization:<p>Tools such as create agent, update agent etc. can update the agent recursively. Let’s assume an agent is chatting with a user and mentions that they only like to communicate in a professional tone. The agent can call a tool to &#x27;update the agent&#x27; and modify&#x2F;update the instructions to include that the user only likes to communicate in a professional tone.<p>This was the reason to create a backend when the market was flooded with agent frameworks. In Julep, you can declare a workflow in YAML, and it can automatically scale Millions of users.

[Other] Open SWE: An open-source asynchronous coding agent <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=TaYVvXbOs8c" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=TaYVvXbOs8c</a><p><a href="https:&#x2F;&#x2F;github.com&#x2F;langchain-ai&#x2F;open-swe" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;langchain-ai&#x2F;open-swe</a>

[Other] Docker for Developers: Essential Commands in One Cheatsheet

[Other] Show HN: Synchrotron, a real-time DSP engine in pure Python Yes, Python.<p>I can already hear the screams from the rafters telling me how terrible of a choice Python is - but in my case, I valued modularity, extensibility, <i>hackability</i> over raw performance. (It was also a challenge to myself to see how far I can get without referencing existing implementations)<p>Synchrotron processes nodes: simple Python classes with typed I&#x2F;O and a render() method for processing. It can be as concise as 5 lines:<p><pre><code> class IncrementNode(Node): input: StreamInput output: StreamOutput def render(self, ctx): self.out.write(self.a.read(ctx) + 1) </code></pre> Nodes can then be spawned and linked programmatically or in the graphical editor. Synchrotron handles the rest at runtime. Besides the web UI, you can also interact with the engine via Python, REST, DSL, or standalone TUI.<p>Currently you can build synths, FX chains, MIDI instruments, arpeggiators, controllers, or just mess about with sound :&gt;<p>Editor: <a href="https:&#x2F;&#x2F;synchrotron.thatother.dev&#x2F;" rel="nofollow">https:&#x2F;&#x2F;synchrotron.thatother.dev&#x2F;</a> Source: <a href="https:&#x2F;&#x2F;github.com&#x2F;ThatOtherAndrew&#x2F;Synchrotron" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;ThatOtherAndrew&#x2F;Synchrotron</a><p>It&#x27;s still experimental (and my first ever shipped project), but I&#x27;d love feedback from people who tinker with audio&#x2F;DSP&#x2F;live coding. Docs are terrible currently, but that&#x27;s my next big goal!

[Other] Show HN: I built a service to run Claude Code in the Cloud

[Other] Turn any website into an API

[Other] Show HN: From Hacking a T480 to the Fastest Open-Hardware 75 Hz E-Ink Display Three years ago, I posted here about hacking together a fast e-ink laptop from a T480 because I was tired of spending all day on LCDs. I liked e-ink’s comfort, but it was too slow for day-to-day use.<p><a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=26245563">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=26245563</a><p>That post drew in people, which grew into a community experimenting with ways to make e-ink usable for everyday computing. That project later turned into a company and a multi-year project to make e-ink fast and open.<p>We built our own FPGA-based controller, Caster, and went through multiple iterations to push past e-ink’s usual limits, slow refresh, ghosting, and proprietary controllers.<p>Now, after three years, we’ve launched the Modos Paper Developer Kit and Monitor: the fastest open-hardware e-ink display, with 75 Hz refresh and sub-100 ms latency.<p>It works with 6&quot; to 13.3&quot; mono or color panels over HDMI or USB-C, supports multiple grayscale modes, and has a C API for low-level control.<p>The hardware, firmware, and schematics are on our GitHub.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;Modos-Labs&#x2F;Glider" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Modos-Labs&#x2F;Glider</a><p>Our goal is to make e-ink fast and open enough that anyone can build on it, for hacking, research, or daily use.<p>Thanks, HN, for being part of the journey.

[Other] Cursor CLI