Open hardware desktop 3D printing is dead?

<a href="https:&#x2F;&#x2F;embassyofthefreemind.com&#x2F;en&#x2F;library&#x2F;online-catalogue&#x2F;?mode=gallery&amp;view=horizontal&amp;sort=random%7B1517048201764%7D%20asc&amp;page=1&amp;fq%5B%5D=search_s_digitized_publication:%22Ja%22&amp;reverse=0" rel="nofollow">https:&#x2F;&#x2F;embassyofthefreemind.com&#x2F;en&#x2F;library&#x2F;online-catalogue...</a>

Occult books digitized and put online by Amsterdam’s Ritman Library

Hi HN,I’ve been working with Kubernetes for over a decade, since the alpha days, and was involved in kube-aws project before AWS launched EKS. For the past four years, I’ve been helping friends and small businesses cut costs by running Kubernetes on Hetzner Cloud, which I’ve found to be rock solid and by far the best priced provider.Provisioning a cluster on Hetzner is now straightforward, thanks to tools like k3s and hetzner-k3s, but configuring it for your specific needs still takes time and expertise. I built Edka to make that part easy: spin up a production ready cluster in ~2 minutes, then choose how low level or automated you want to go.How it works:Layer 1 – Cluster provisioning
 - Creates a k3s-based Kubernetes cluster on Hetzner (lightweight, easy to manage, scales well).Layer 2 – Add-ons
 - One-click deploy for metrics-server, cert-manager, and various operators; preconfigured for Hetzner, no extra setup needed.Layer 3 – Applications
 - Minimal config UIs for apps built on top of add-ons.
 - Example: Need PostgreSQL? Fill a few fields → platform installs CloudNativePG → provisions HA PostgreSQL with PITR → gives ready to use endpoints. Backups can be restored to any point in time with a click. Quick demo: <a href="https:&#x2F;&#x2F;edka.io&#x2F;apps&#x2F;" rel="nofollow">https:&#x2F;&#x2F;edka.io&#x2F;apps&#x2F;</a>Layer 4 – Deployments
 - Connect your CI to push container images to a public&#x2F;private registry.
 - Edka updates deployments automatically (with semantic versioning rules), supports instant rollbacks, autoscaling, persistent volumes, secrets&#x2F;env imports, and quick public exposure. Quick demo: <a href="https:&#x2F;&#x2F;edka.io&#x2F;deployments&#x2F;" rel="nofollow">https:&#x2F;&#x2F;edka.io&#x2F;deployments&#x2F;</a>Tech stack: TypeScript, React + Tailwind CSS, PostgreSQL, Redis, BullMQ, Vault + AWS KMS to encrypted sensitive data.The platform is still in beta and I’m building it in my spare time, so there are some rough edges, but I’d love feedback from anyone running Kubernetes on Hetzner, exploring alternatives to EKS&#x2F;GKE&#x2F;AKS or looking to automate their infrastructure with Kubernetes.More details: <a href="https:&#x2F;&#x2F;edka.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;edka.io&#x2F;</a>Thank you!

Show HN: Edka – Kubernetes clusters on your own Hetzner account

Do Things That Don't Scale (2013)

The electric fence stopped working years ago

Imagen 4 is now generally available

Vaultwarden commit introduces SSO using OpenID Connect

Claude Opus 4 and 4.1 can now end a rare subset of conversations

ADHD drug treatment and risk of negative events and outcomes

ARM adds neural accelerators to GPUs

Compiler Bug Causes Compiler Bug: How a 12-Year-Old G++ Bug Took Down Solidity

OpenBSD is so fast, I had to modify the program slightly to measure itself

When the CIA got away with building a heart attack gun

US F-16s lose out as Thai Air Force seals US$600M deal for Swedish Gripen jets

Bullfrog in the Dungeon

The Future of Large Files in Git Is Git

Is air travel getting worse?

Hey HN - We’re Bob and Ethan from Embedder (<a href="https:&#x2F;&#x2F;embedder.dev">https:&#x2F;&#x2F;embedder.dev</a>), a hardware-aware AI coding agent that can write firmware and test it on physical hardware.Here’s a demo in which we integrate a magnetometer for the Pebble 2 smartwatch: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=WOpAfeiFQkQ" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=WOpAfeiFQkQ</a>We were frustrated by the gap between coding agents and the realities of writing firmware. We&#x27;d ask Cursor to, say, write an I2C driver for a new sensor on an STM32, and it would confidently spit out code that used non-existent registers or HAL functions from the wrong chip family. It had no context, so it would just guess and the code is always wrong.Even when it wrote the right code, the agent had no way of interacting with your board and the developer would have to manually test it and prompt the agent again to fix any bugs they found. Making current solutions not ideal when working in an embedded context.That’s why we are building Embedder, a hardware-aware coding agent that is optimized for work in embedded contexts. It understands your datasheets and schematics and can also flash and test on your hardware.First, you give it context by uploading datasheets, reference manuals, schematics, or any other documentation on our web console and our coding agent will automatically have context when it executes tasks in the command line.Second, Embedder can directly interact with your hardware to close the development loop. The agent is able to use a serial console just like a regular developer to read from your board and verify outputs. To solve more complex bugs or identify hardware issues the coding agent is also able to launch a debugging agent optimized for step through debugging workloads and interact with local or remote gbdservers.You can try it out today. It’s an npm package you can install and run from your terminal:<pre><code> npm i -g @embedder&#x2F;embedder &amp;&amp; embedder
</code></pre>
It&#x27;s free for the rest of this month while we&#x27;re in beta. After that, we&#x27;re planning a usage based model for individual developers and a team plan with more advanced features.We’d love to get feedback from the community, or hear about your experiences of embedded development. We’ll be in the comments to respond!

Launch HN: Embedder (YC S25) – Claude code for embedded software

An interactive guide to sensor fusion with quaternions

I accidentally became PureGym’s unofficial Apple Wallet developer