The best Hacker News stories from Show from the past day
Latest posts:
Show HN: Building better base images
This project addresses the inefficiencies of traditional Dockerfile-based container builds where each customization layer creates storage bloat through duplicate dependencies from repeated apt-get install commands, network inefficiency from redundant package downloads across different images, and slow iteration cycles requiring full rebuilds of all previous steps. Our solution enables building minimal base images from scratch using debootstrap that precisely include only required components in the initial build, while allowing creation of specialized variants (Java, Kafka, etc.) from these common foundations - resulting in significantly leaner images, faster builds, and more efficient resource utilization compared to standard Docker layer stacking approaches.
Show HN: Building better base images
This project addresses the inefficiencies of traditional Dockerfile-based container builds where each customization layer creates storage bloat through duplicate dependencies from repeated apt-get install commands, network inefficiency from redundant package downloads across different images, and slow iteration cycles requiring full rebuilds of all previous steps. Our solution enables building minimal base images from scratch using debootstrap that precisely include only required components in the initial build, while allowing creation of specialized variants (Java, Kafka, etc.) from these common foundations - resulting in significantly leaner images, faster builds, and more efficient resource utilization compared to standard Docker layer stacking approaches.
Show HN: I built an app that reduces podcast preparation effort by 95% +
Show HN: Time Travel with Your SQL
Hi, my name is Anguel and I am one of the developers of WhoDB (<a href="https://github.com/clidey/whodb">https://github.com/clidey/whodb</a>)<p>I am not a fan of the dbeaver, beekeeper, adminer, etc experience because they are bloated, ugly, and at best okay but not great.<p>Hence why I started working on WhoDB.<p>The approach:<p>- browser-based (chrome/firefox)<p>- no bloat<p>- jupyter notebook-like experience (Scratchpad)<p>- built-in AI co-pilot with ollama (local) or openai/anthropic<p>We just shipped query history and replay (time travel?) to the Scratchpad.<p>Would love for you to check it out and give some feedback aka roast us into oblivion:<p>docker run -p 8080:8080 clidey/whodb<p>Food for thought:<p>1. What's your biggest database pain point?<p>2. Any killer feature missing from current tools?
Show HN: Time Travel with Your SQL
Hi, my name is Anguel and I am one of the developers of WhoDB (<a href="https://github.com/clidey/whodb">https://github.com/clidey/whodb</a>)<p>I am not a fan of the dbeaver, beekeeper, adminer, etc experience because they are bloated, ugly, and at best okay but not great.<p>Hence why I started working on WhoDB.<p>The approach:<p>- browser-based (chrome/firefox)<p>- no bloat<p>- jupyter notebook-like experience (Scratchpad)<p>- built-in AI co-pilot with ollama (local) or openai/anthropic<p>We just shipped query history and replay (time travel?) to the Scratchpad.<p>Would love for you to check it out and give some feedback aka roast us into oblivion:<p>docker run -p 8080:8080 clidey/whodb<p>Food for thought:<p>1. What's your biggest database pain point?<p>2. Any killer feature missing from current tools?
Show HN: Atari Missile Command Game Built Using AI Gemini 2.5 Pro
A modern HTML5 canvas remake of the classic Atari game from 1980. Defend your cities and missile bases from incoming enemy attacks using your missile launchers. Initially built using the Google Gemini 2.5 Pro AI LLM model.
Show HN: Atari Missile Command Game Built Using AI Gemini 2.5 Pro
A modern HTML5 canvas remake of the classic Atari game from 1980. Defend your cities and missile bases from incoming enemy attacks using your missile launchers. Initially built using the Google Gemini 2.5 Pro AI LLM model.
Show HN: Atari Missile Command Game Built Using AI Gemini 2.5 Pro
A modern HTML5 canvas remake of the classic Atari game from 1980. Defend your cities and missile bases from incoming enemy attacks using your missile launchers. Initially built using the Google Gemini 2.5 Pro AI LLM model.
Show HN: Fermi – A Wordle-style game for order-of-magnitude thinking
I always thought it was cool when someone could make a plausible estimate from reasonable guesses. I recently learned that these are sometimes named after Enrico Fermi, the famous physicist, and its the same technique used to create his famous Fermi paradox.<p>You build a rough logic chain using a few sliders and fixed quantities (e.g. weeks per year), and the goal is to get within an order of magnitude of the true answer. The math is simple; the thinking is the game.<p>Would love feedback.
Show HN: I turned my kid's worksheet into a math game in 10 minutes with Claude
Show HN: I built a Yahoo Messenger-inspired web chat app – pure nostalgia
I’ve been feeling a bit nostalgic lately, so I decided to build a little web chat app inspired by Yahoo! Messenger. Right now it’s got group chat rooms. Super simple setup, no email required to register. You can create your own room or hop into one that’s already open.<p>Room owners can customize things like backgrounds and even cursors of their room. Users can format their messages with basic markdown like bold, italics, and color texts (kind of like the old Yahoo! days).<p>I even brought back the classic Yahoo! Messenger emoticons because… well, why not?<p>You can try it out here: <a href="https://buzzed.chat" rel="nofollow">https://buzzed.chat</a>
(Heads up: it's still pretty barebones, so excuse any bugs you might run into!)<p>I'm thinking of adding a few more features next, like:<p>• Audibles<p>• A buddy list so you can add friends<p>• Private chats between buddies<p>Before I keep building, I wanted to check in and see what people think. Anyone else remember using Yahoo! Messenger back in the day? Any features you’d love to see again?<p>Would genuinely love to hear your thoughts and ideas
Show HN: Obelisk – a WASM-based deterministic workflow engine
A lightweight engine for durable execution / deterministic workflows I built with Rust, wasmtime and the WASM Component Model.
Its main use is running reliable, long-running workflows that can automatically resume after failures.
Looking for feedback on the approach and potential use cases!
Show HN: Obelisk – a WASM-based deterministic workflow engine
A lightweight engine for durable execution / deterministic workflows I built with Rust, wasmtime and the WASM Component Model.
Its main use is running reliable, long-running workflows that can automatically resume after failures.
Looking for feedback on the approach and potential use cases!
Show HN: I built a tool to manage and compare credit card rewards
This is a free tool that helps you manage and visualize your credit card rewards across different categories.<p>You can input the cards in your wallet and see how they complement each other, spot gaps in your setup, and also see the best card to use for a given merchant.<p>I’m also a founder at OneCard, where we’re building a smart card that’ll eventually handle all of this automatically, routing each purchase to the best card in real-time.<p>Would love feedback from the HN community!
Show HN: I built a tool to manage and compare credit card rewards
This is a free tool that helps you manage and visualize your credit card rewards across different categories.<p>You can input the cards in your wallet and see how they complement each other, spot gaps in your setup, and also see the best card to use for a given merchant.<p>I’m also a founder at OneCard, where we’re building a smart card that’ll eventually handle all of this automatically, routing each purchase to the best card in real-time.<p>Would love feedback from the HN community!
Show HN: I built a tool to manage and compare credit card rewards
This is a free tool that helps you manage and visualize your credit card rewards across different categories.<p>You can input the cards in your wallet and see how they complement each other, spot gaps in your setup, and also see the best card to use for a given merchant.<p>I’m also a founder at OneCard, where we’re building a smart card that’ll eventually handle all of this automatically, routing each purchase to the best card in real-time.<p>Would love feedback from the HN community!
Show HN: Koreo – A platform engineering toolkit for Kubernetes
A large part of our (Real Kinetic's) business is helping organizations implement platform engineering, but we've found the existing tooling to be lacking. For IaC, Terraform state becomes a pain because TF treats infrastructure as "one-shot" commands. The Kubernetes controller model provides a nicer approach to managing infrastructure, but the tooling here is also lacking. For configuration management, Helm just doesn't really scale with complexity, nor does Kustomize. For resource orchestration, Crossplane is a step in the right direction but still has challenges and limitations.<p>As a result, we ended up building something that's sort of a "meta-controller programming language" on top of Kubernetes called Koreo. It provides a solution for configuration management and resource orchestration in Kubernetes by basically letting you program controllers. We've been using Koreo for a while now to build internal developer platform capabilities for our commercial product and our clients, and we recently open sourced it to share it with the community.<p>Koreo has some similarities to configuration languages like KCL, Jsonnet, etc. since it is a means of configuration management (e.g. you can define base configurations, apply overlays, point patches, and so forth). Where it really diverges though is Koreo provides a unified approach to config management <i>and</i> resource orchestration. This means you can start to treat Kubernetes resources as "legos" to build pretty sophisticated workflows. For instance, the output of a resource can be used as the input to another resource. This isn't really possible with Helm, even with `lookup` because `lookup` requires the resource to already be in-cluster in order to reference it.<p>This is why we refer to Koreo as a meta-controller programming language because it effectively lets you program and compose Kubernetes controllers into cohesive platforms—either built-in controllers (think Deployment or StatefulSet), off-the-shelf ones such as AWS ACK or GCP's Config Connector, or custom operators. It lets you build or combine controllers without actually needing to implement an operator. Through this lens, Koreo is really more akin to Crossplane but without some of the limitations such as Providers and cluster-scoped managed resources.<p>It seems crazy and maybe it is, but I've found working in Koreo to actually be surprisingly fun since it kind of turns Kubernetes primitives into legos you can easily piece together, reuse, and build some pretty cool automated workflows. You can learn more about the motivation and thinking behind it here: <a href="https://theyamlengineer.com" rel="nofollow">https://theyamlengineer.com</a>
Show HN: Koreo – A platform engineering toolkit for Kubernetes
A large part of our (Real Kinetic's) business is helping organizations implement platform engineering, but we've found the existing tooling to be lacking. For IaC, Terraform state becomes a pain because TF treats infrastructure as "one-shot" commands. The Kubernetes controller model provides a nicer approach to managing infrastructure, but the tooling here is also lacking. For configuration management, Helm just doesn't really scale with complexity, nor does Kustomize. For resource orchestration, Crossplane is a step in the right direction but still has challenges and limitations.<p>As a result, we ended up building something that's sort of a "meta-controller programming language" on top of Kubernetes called Koreo. It provides a solution for configuration management and resource orchestration in Kubernetes by basically letting you program controllers. We've been using Koreo for a while now to build internal developer platform capabilities for our commercial product and our clients, and we recently open sourced it to share it with the community.<p>Koreo has some similarities to configuration languages like KCL, Jsonnet, etc. since it is a means of configuration management (e.g. you can define base configurations, apply overlays, point patches, and so forth). Where it really diverges though is Koreo provides a unified approach to config management <i>and</i> resource orchestration. This means you can start to treat Kubernetes resources as "legos" to build pretty sophisticated workflows. For instance, the output of a resource can be used as the input to another resource. This isn't really possible with Helm, even with `lookup` because `lookup` requires the resource to already be in-cluster in order to reference it.<p>This is why we refer to Koreo as a meta-controller programming language because it effectively lets you program and compose Kubernetes controllers into cohesive platforms—either built-in controllers (think Deployment or StatefulSet), off-the-shelf ones such as AWS ACK or GCP's Config Connector, or custom operators. It lets you build or combine controllers without actually needing to implement an operator. Through this lens, Koreo is really more akin to Crossplane but without some of the limitations such as Providers and cluster-scoped managed resources.<p>It seems crazy and maybe it is, but I've found working in Koreo to actually be surprisingly fun since it kind of turns Kubernetes primitives into legos you can easily piece together, reuse, and build some pretty cool automated workflows. You can learn more about the motivation and thinking behind it here: <a href="https://theyamlengineer.com" rel="nofollow">https://theyamlengineer.com</a>
Show HN: Koreo – A platform engineering toolkit for Kubernetes
A large part of our (Real Kinetic's) business is helping organizations implement platform engineering, but we've found the existing tooling to be lacking. For IaC, Terraform state becomes a pain because TF treats infrastructure as "one-shot" commands. The Kubernetes controller model provides a nicer approach to managing infrastructure, but the tooling here is also lacking. For configuration management, Helm just doesn't really scale with complexity, nor does Kustomize. For resource orchestration, Crossplane is a step in the right direction but still has challenges and limitations.<p>As a result, we ended up building something that's sort of a "meta-controller programming language" on top of Kubernetes called Koreo. It provides a solution for configuration management and resource orchestration in Kubernetes by basically letting you program controllers. We've been using Koreo for a while now to build internal developer platform capabilities for our commercial product and our clients, and we recently open sourced it to share it with the community.<p>Koreo has some similarities to configuration languages like KCL, Jsonnet, etc. since it is a means of configuration management (e.g. you can define base configurations, apply overlays, point patches, and so forth). Where it really diverges though is Koreo provides a unified approach to config management <i>and</i> resource orchestration. This means you can start to treat Kubernetes resources as "legos" to build pretty sophisticated workflows. For instance, the output of a resource can be used as the input to another resource. This isn't really possible with Helm, even with `lookup` because `lookup` requires the resource to already be in-cluster in order to reference it.<p>This is why we refer to Koreo as a meta-controller programming language because it effectively lets you program and compose Kubernetes controllers into cohesive platforms—either built-in controllers (think Deployment or StatefulSet), off-the-shelf ones such as AWS ACK or GCP's Config Connector, or custom operators. It lets you build or combine controllers without actually needing to implement an operator. Through this lens, Koreo is really more akin to Crossplane but without some of the limitations such as Providers and cluster-scoped managed resources.<p>It seems crazy and maybe it is, but I've found working in Koreo to actually be surprisingly fun since it kind of turns Kubernetes primitives into legos you can easily piece together, reuse, and build some pretty cool automated workflows. You can learn more about the motivation and thinking behind it here: <a href="https://theyamlengineer.com" rel="nofollow">https://theyamlengineer.com</a>
Show HN: Koreo – A platform engineering toolkit for Kubernetes
A large part of our (Real Kinetic's) business is helping organizations implement platform engineering, but we've found the existing tooling to be lacking. For IaC, Terraform state becomes a pain because TF treats infrastructure as "one-shot" commands. The Kubernetes controller model provides a nicer approach to managing infrastructure, but the tooling here is also lacking. For configuration management, Helm just doesn't really scale with complexity, nor does Kustomize. For resource orchestration, Crossplane is a step in the right direction but still has challenges and limitations.<p>As a result, we ended up building something that's sort of a "meta-controller programming language" on top of Kubernetes called Koreo. It provides a solution for configuration management and resource orchestration in Kubernetes by basically letting you program controllers. We've been using Koreo for a while now to build internal developer platform capabilities for our commercial product and our clients, and we recently open sourced it to share it with the community.<p>Koreo has some similarities to configuration languages like KCL, Jsonnet, etc. since it is a means of configuration management (e.g. you can define base configurations, apply overlays, point patches, and so forth). Where it really diverges though is Koreo provides a unified approach to config management <i>and</i> resource orchestration. This means you can start to treat Kubernetes resources as "legos" to build pretty sophisticated workflows. For instance, the output of a resource can be used as the input to another resource. This isn't really possible with Helm, even with `lookup` because `lookup` requires the resource to already be in-cluster in order to reference it.<p>This is why we refer to Koreo as a meta-controller programming language because it effectively lets you program and compose Kubernetes controllers into cohesive platforms—either built-in controllers (think Deployment or StatefulSet), off-the-shelf ones such as AWS ACK or GCP's Config Connector, or custom operators. It lets you build or combine controllers without actually needing to implement an operator. Through this lens, Koreo is really more akin to Crossplane but without some of the limitations such as Providers and cluster-scoped managed resources.<p>It seems crazy and maybe it is, but I've found working in Koreo to actually be surprisingly fun since it kind of turns Kubernetes primitives into legos you can easily piece together, reuse, and build some pretty cool automated workflows. You can learn more about the motivation and thinking behind it here: <a href="https://theyamlengineer.com" rel="nofollow">https://theyamlengineer.com</a>