🛠️ All DevTools

[API/SDK] Muxio: Rust layered stream and RPC toolkit

[Other] The Death of the Middle-Class Musician

Schizophrenia is the price we pay for minds poised near the edge of a cliff

[CLI Tool] Show HN: Vet – A tool for safely running remote shell scripts

[Code Quality] Show HN: Query your Rust codebase and generate types for anything Hello HN!<p>As a long-time professional Rust developer. I&#x27;ve always been frustrated by the difficulty and &quot;hackiness&quot; of producing bindings to other languages, whether a frontend, an FFI library, etc.<p>Not just in Rust but in any language.<p>After many years of trying existing solutions and trying to make my own, I&#x27;ve finally developed a solution I&#x27;m very happy with.<p>RTK (aka Rust Type Kit) allows you to write Lua scripts that perform queries on your code, such as method calls to Axum&#x27;s `.route`, function definitions, and more, and then receive rich type information including all argument types, function paths, proc macro attributes, and more.<p>Your Lua script can then read this information and emit an output file in any language of your choosing. Or, you can emit compiler errors and use it as a linter of sorts. You can even directly re-emit Rust code itself and use this as a richer proc macro solution!<p>The code example is a bit verbose, so I encourage you to take a look at the repo&#x27;s README. I look forward to hearing your thoughts, or any usecases you may come up with!

Life of an inference request (vLLM V1): How LLMs are served efficiently at scale

[CLI Tool] Show HN: Clai - Vendor agnostic Claude Code/Gemini CLI written in Go

MCP: An (Accidentally) Universal Plugin System

[Other] We ran a Unix-like OS on our home-built CPU with a home-built C compiler (2020)

[IDE/Editor] Show HN: Reactylon – Open-source framework for building 3D/XR apps with React

[Build/Deploy] Cross-Compiling Common Lisp for Windows

Show HN: I'm an airline pilot – I built interactive graphs/globes of my flights Hey HN!<p>Pilots everywhere are required to keep a logbook of all their flying hours, aircraft, airports, and so on. Since I track everything digitally (some people still just use paper logbooks!), I put together some data visualizations and a few 3D globes to show my flying history.<p>This globe is probably my favourite so far: <a href="https:&#x2F;&#x2F;jameshard.ing&#x2F;pilot&#x2F;globes&#x2F;all" rel="nofollow">https:&#x2F;&#x2F;jameshard.ing&#x2F;pilot&#x2F;globes&#x2F;all</a><p>If you’ve got ideas for other graphs or ways to show this kind of data, I’d love to hear them!

[CLI Tool] Show HN: Zenta – Mindfulness for Terminal Users

Show HN: Sink – Sync any directory with any device on your local network i made sink. it&#x27;s a simple little tool that continuously syncs folders between 2 devices. no cloud, no email, flash drives, no bs.<p>it just uses your local wifi. run it on your machines, tell them to trust each other, and you&#x27;re set. and if you manage to edit the same file at once, it handles the conflict and saves both copies.<p>for anyone who just wants to get files from point a to b without the headache. hope it makes your life a bit less annoying.<p>github: <a href="https:&#x2F;&#x2F;github.com&#x2F;sirbread&#x2F;sink">https:&#x2F;&#x2F;github.com&#x2F;sirbread&#x2F;sink</a> binary: <a href="https:&#x2F;&#x2F;github.com&#x2F;sirbread&#x2F;sink&#x2F;releases&#x2F;tag&#x2F;v0.1">https:&#x2F;&#x2F;github.com&#x2F;sirbread&#x2F;sink&#x2F;releases&#x2F;tag&#x2F;v0.1</a>

Modelling API rate limits as diophantine inequalities

Brad Woods Digital Garden

Amber insect fossils reveal "zombie" fungi likely lived alongside dinosaurs

[Other] Show HN: PRSS Site Creator – Create Blogs and Websites from Your Desktop

[Testing] Show HN: Magnitude – Open-source AI browser automation framework Hey HN, Anders and Tom here. We had a post about our AI test automation framework 2 months ago that got a decent amount of traction (<a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=43796003">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=43796003</a>).<p>We got some great feedback from the community, with the most positive response being about our vision-first approach used in our browser agent. However, many wanted to use the underlying agent outside the testing domain. So today, we&#x27;re releasing our fully featured AI browser automation framework.<p>You can use it to automate tasks on the web, integrate between apps without APIs, extract data, test your web apps, or as a building block for your own browser agents.<p>Traditionally, browser automation could only be done via the DOM, even though that’s not how humans use browsers. Most browser agents are still stuck in this paradigm. With a vision-first approach, we avoid relying on flaky DOM navigation and perform better on complex interactions found in a broad variety of sites, for example:<p>- Drag and drop interactions<p>- Data visualizations, charts, and tables<p>- Legacy apps with nested iframes<p>- Canvas and webGL-heavy sites (like design tools or photo editing)<p>- Remote desktops streamed into the browser<p>To interact accurately with the browser, we use visually grounded models to execute precise actions based on pixel coordinates. The model used by Magnitude must be smart enough to plan out actions but also able to execute them. Not many models are both smart *and* visually grounded. We highly recommend Claude Sonnet 4 for the best performance, but if you prefer open source, we also support Qwen-2.5-VL 72B.<p>Most browser agents never make it to production. This is because of (1) the flaky DOM navigation mentioned above, but (2) the lack of control most browser agents offer. The dominant paradigm is you give the agent a high-level task + tools and hope for the best. This quickly falls apart for production automations that need to be reliable and specific. With Magnitude, you have fine-grained control over the agent with our `act()` and `extract()` syntax, and can mix it with your own code as needed. You also have full control of the prompts at both the action and agent level.<p>```ts<p>&#x2F;&#x2F; Magnitude can handle high-level tasks<p>await agent.act(&#x27;Create an issue&#x27;, {<p><pre><code> &#x2F;&#x2F; Optionally pass data that the agent will use where appropriate data: { title: &#x27;Use Magnitude&#x27;, description: &#x27;Run &quot;npx create-magnitude-app&quot; and follow the instructions&#x27;, }, </code></pre> });<p>&#x2F;&#x2F; It can also handle low-level actions<p>await agent.act(&#x27;Drag &quot;Use Magnitude&quot; to the top of the in progress column&#x27;);<p>&#x2F;&#x2F; Intelligently extract data based on the DOM content matching a provided zod schema<p>const tasks = await agent.extract(<p><pre><code> &#x27;List in progress issues&#x27;, z.array(z.object({ title: z.string(), description: z.string(), &#x2F;&#x2F; Agent can extract existing data or new insights difficulty: z.number().describe(&#x27;Rate the difficulty between 1-5&#x27;) })), </code></pre> );<p>```<p>We have a setup script that makes it trivial to get started with an example, just run &quot;npx create-magnitude-app&quot;. We’d love to hear what you think!<p>Repo: <a href="https:&#x2F;&#x2F;github.com&#x2F;magnitudedev&#x2F;magnitude">https:&#x2F;&#x2F;github.com&#x2F;magnitudedev&#x2F;magnitude</a>

[DevOps] Building untrusted container images safely at scale