The best Hacker News stories from All from the past day
Latest posts:
Linux Kernel Explorer
TPUs vs. GPUs and why Google is positioned to win AI race in the long term
We're losing our voice to LLMs
DIY NAS: 2026 Edition
Penpot: The Open-Source Figma
Tell HN: Happy Thanksgiving
I’ve been a part of this community for fifteen years. Despite the yearly bemoaning of HN’s quality compared to its mythical past, I’ve found that it’s the one community that has remained steadfast as a source of knowledge, cattiness, and good discussion.<p>Thank you @dang and @tomhow.<p>Here's to another year.
Bring bathroom doors back to hotels
Migrating the main Zig repository from GitHub to Codeberg
S&box is now an open source game engine
Don't Download Apps
The EU made Apple adopt new Wi-Fi standards, and now Android can support AirDrop
The EU made Apple adopt new Wi-Fi standards, and now Android can support AirDrop
OpenAI needs to raise at least $207B by 2030
I don't care how well your "AI" works
Voyager 1 is about to reach one light-day from Earth
Voyager 1 is about to reach one light-day from Earth
Someone at YouTube Needs Glasses: The Prophecy Has Been Fulfilled
Related: <i>Someone at YouTube needs glasses</i> - <a href="https://news.ycombinator.com/item?id=43846487">https://news.ycombinator.com/item?id=43846487</a> - April 2025 (694 comments)
Show HN: We built an open source, zero webhooks payment processor
Hi HN! For the past bit we’ve been building Flowglad (<a href="https://flowglad.com">https://flowglad.com</a>) and can now feel it’s just gotten good enough to share with you all:<p>Repo: <a href="https://github.com/flowglad/flowglad" rel="nofollow">https://github.com/flowglad/flowglad</a><p>Demo video: <a href="https://www.youtube.com/watch?v=G6H0c1Cd2kU" rel="nofollow">https://www.youtube.com/watch?v=G6H0c1Cd2kU</a><p>Flowglad is a payment processor that you integrate without writing any glue code. Along with processing your payments, it tells you in real time the features and usage credit balances that your customers have available to you based on their billing state. The DX feels like React, because we wanted to bring the reactive programming paradigm to payments.<p>We make it easy to spin up full-fledged pricing models (including usage meters, feature gates and usage credit grants) in a few clicks. We schematize these pricing models into a pricing.yaml file that’s kinda like Terraform but for your pricing.<p>The result is a payments layer that AI coding agents have a substantially easier time one-shotting (for now the happiest path is a fullstack Typescript + React app).<p>Why we built this:<p>- After a decade of building on Stripe, we found it powerful but underopinionated. It left us doing a lot of rote work to set up fairly standard use cases
- That meant more code to maintain, much of which is brittle because it crosses so many server-client boundaries
- Not to mention choreographing the lifecycle of our business domain with the Stripe checkout flow and webhook event types, of which there are 250+
- Payments online has gotten complex - not just new pricing models for AI products, but also cross border sales tax, etc. You either need to handle significant chunks of it yourself, or sign up for and compose multiple services<p>This all feels unduly clunky, esp when compared to how easy other layers like hosting and databases have gotten in recent years.<p>These patterns haven’t changed much in a decade. And while coding agents can nail every other rote part of an app (auth, db, analytics), payments is the scariest to tab-tab-tab your way through. Because the the existing integration patterns are difficult to reason about, difficult to verify correctness, and absolutely mission critical.<p>Our beta version lets you:<p>- Spin up common pricing models in just a few clicks, and customize them as needed
- Clone pricing models between testmode and live mode, and import / export via pricing.yaml
- Check customer usage credits and feature access in real time on your backend and React frontend
- Integrate without any DB schema changes - you reference your customers via your ids, and reference prices, products, features and usage meters via slugs that you define<p>We’re still early in our journey so would love your feedback and opinions. Billing has a lot of use cases, so if you see anything that you wish we supported, please let us know!
APT Rust requirement raises questions
Human brains are preconfigured with instructions for understanding the world