The best Hacker News stories from Show from the past day

from

All Show

from the past*

day week month

with these search terms:

Create follow Go back

Latest posts:

Show HN: Chebyshev approximation calculator

Hi everyone,<p>here's a web app I made that generates code for efficiently approximating mathematical functions. This is useful when performance matters more than perfect accuracy, for example in embedded systems.<p>The app uses Chebyshev expansions, which despite their theoretical depth result in suprisingly compact and readable code in practice. This code is generated for you and using it does not require any knowledge of the underlying theory.<p>Source code and more info: <a href="https://github.com/stuffmatic/chebyshev-calculator">https://github.com/stuffmatic/chebyshev-calculator</a>

Show HN: Chebyshev approximation calculator

Hi everyone,<p>here's a web app I made that generates code for efficiently approximating mathematical functions. This is useful when performance matters more than perfect accuracy, for example in embedded systems.<p>The app uses Chebyshev expansions, which despite their theoretical depth result in suprisingly compact and readable code in practice. This code is generated for you and using it does not require any knowledge of the underlying theory.<p>Source code and more info: <a href="https://github.com/stuffmatic/chebyshev-calculator">https://github.com/stuffmatic/chebyshev-calculator</a>

Show HN: Chebyshev approximation calculator

Hi everyone,<p>here's a web app I made that generates code for efficiently approximating mathematical functions. This is useful when performance matters more than perfect accuracy, for example in embedded systems.<p>The app uses Chebyshev expansions, which despite their theoretical depth result in suprisingly compact and readable code in practice. This code is generated for you and using it does not require any knowledge of the underlying theory.<p>Source code and more info: <a href="https://github.com/stuffmatic/chebyshev-calculator">https://github.com/stuffmatic/chebyshev-calculator</a>

Show HN: One – A new React framework unifying web, native and local-first

Hey HN, I'm Nate, the creator of Tamagui.<p>One is a React framework that does two things differently in hopes of simplifying how we build websites and apps:<p>1. It unifies React Native and React web with typed file system routing by making Vite able to serve RN. This lets you share (or diverge) your code in a simpler way for cross-platform apps.<p>2. We've partnered with Zero (<a href="https://zerosync.dev" rel="nofollow">https://zerosync.dev</a>) to make local-first work well. We've been building a solution in One that makes Zero supporting server rendering, without waterfalls, and with seamless server/client handoff.<p>---<p>Honestly - I'm a bit hesitant to post One here.<p>HN has really soured on frontend/frameworks. And I get it. We've collectively complicated the hell out of things.<p>That's why I decided to build One. I loved Rails, it made me as a young developer able to finally realize way more ambitious projects than I'd ever done before. I also liked the promise (not implementation) of Meteor - it felt like the clear future, I guess just a bit too early (and a bit too scope-creeped).<p>I worked at Uniswap and built Tamagui and so spent a lot of time building cross-platform apps that share code. Uniswap is built on Tamagui and I think proves you <i>can</i> make really high quality UX while sharing a lot of code - but it's insanely hard and requires a huge team. My goal with One is to make what is now possible but hard dramatically easier.<p>And I think the path to there goes through local-first, because it makes building super responsive apps much, much simpler, and Zero is the first library to actually pull it off in a way that doesn't bloat your bundle or have very limiting constraints.<p>I happened to live down the street from Aaron, one of the founders of Zero, in our tiny town in Hawaii. We talked a lot about Zero over the last couple years, and I found it really admirable how he consistently chose the "harder but better" path in building it. It really shaped into something incredible, and that convinced me to actually launch One, which at the time was more of an experiment.<p>I can see a lot of potential criticism - do we need yet another framework, this is too shiny and vaporware-y, this is just more complexity and abstraction, etc. Happy to respond to those comments if they come.<p>I'm just building out something that I've been wanting for a long time. Opinionated enough to let me move fast like Rails, but leaning on the great work of team Zero so that we don't end up with the scope creep of Meteor. And honestly, it's just really fun to hack on.

Show HN: One – A new React framework unifying web, native and local-first

Hey HN, I'm Nate, the creator of Tamagui.<p>One is a React framework that does two things differently in hopes of simplifying how we build websites and apps:<p>1. It unifies React Native and React web with typed file system routing by making Vite able to serve RN. This lets you share (or diverge) your code in a simpler way for cross-platform apps.<p>2. We've partnered with Zero (<a href="https://zerosync.dev" rel="nofollow">https://zerosync.dev</a>) to make local-first work well. We've been building a solution in One that makes Zero supporting server rendering, without waterfalls, and with seamless server/client handoff.<p>---<p>Honestly - I'm a bit hesitant to post One here.<p>HN has really soured on frontend/frameworks. And I get it. We've collectively complicated the hell out of things.<p>That's why I decided to build One. I loved Rails, it made me as a young developer able to finally realize way more ambitious projects than I'd ever done before. I also liked the promise (not implementation) of Meteor - it felt like the clear future, I guess just a bit too early (and a bit too scope-creeped).<p>I worked at Uniswap and built Tamagui and so spent a lot of time building cross-platform apps that share code. Uniswap is built on Tamagui and I think proves you <i>can</i> make really high quality UX while sharing a lot of code - but it's insanely hard and requires a huge team. My goal with One is to make what is now possible but hard dramatically easier.<p>And I think the path to there goes through local-first, because it makes building super responsive apps much, much simpler, and Zero is the first library to actually pull it off in a way that doesn't bloat your bundle or have very limiting constraints.<p>I happened to live down the street from Aaron, one of the founders of Zero, in our tiny town in Hawaii. We talked a lot about Zero over the last couple years, and I found it really admirable how he consistently chose the "harder but better" path in building it. It really shaped into something incredible, and that convinced me to actually launch One, which at the time was more of an experiment.<p>I can see a lot of potential criticism - do we need yet another framework, this is too shiny and vaporware-y, this is just more complexity and abstraction, etc. Happy to respond to those comments if they come.<p>I'm just building out something that I've been wanting for a long time. Opinionated enough to let me move fast like Rails, but leaning on the great work of team Zero so that we don't end up with the scope creep of Meteor. And honestly, it's just really fun to hack on.

Show HN: One – A new React framework unifying web, native and local-first

Hey HN, I'm Nate, the creator of Tamagui.<p>One is a React framework that does two things differently in hopes of simplifying how we build websites and apps:<p>1. It unifies React Native and React web with typed file system routing by making Vite able to serve RN. This lets you share (or diverge) your code in a simpler way for cross-platform apps.<p>2. We've partnered with Zero (<a href="https://zerosync.dev" rel="nofollow">https://zerosync.dev</a>) to make local-first work well. We've been building a solution in One that makes Zero supporting server rendering, without waterfalls, and with seamless server/client handoff.<p>---<p>Honestly - I'm a bit hesitant to post One here.<p>HN has really soured on frontend/frameworks. And I get it. We've collectively complicated the hell out of things.<p>That's why I decided to build One. I loved Rails, it made me as a young developer able to finally realize way more ambitious projects than I'd ever done before. I also liked the promise (not implementation) of Meteor - it felt like the clear future, I guess just a bit too early (and a bit too scope-creeped).<p>I worked at Uniswap and built Tamagui and so spent a lot of time building cross-platform apps that share code. Uniswap is built on Tamagui and I think proves you <i>can</i> make really high quality UX while sharing a lot of code - but it's insanely hard and requires a huge team. My goal with One is to make what is now possible but hard dramatically easier.<p>And I think the path to there goes through local-first, because it makes building super responsive apps much, much simpler, and Zero is the first library to actually pull it off in a way that doesn't bloat your bundle or have very limiting constraints.<p>I happened to live down the street from Aaron, one of the founders of Zero, in our tiny town in Hawaii. We talked a lot about Zero over the last couple years, and I found it really admirable how he consistently chose the "harder but better" path in building it. It really shaped into something incredible, and that convinced me to actually launch One, which at the time was more of an experiment.<p>I can see a lot of potential criticism - do we need yet another framework, this is too shiny and vaporware-y, this is just more complexity and abstraction, etc. Happy to respond to those comments if they come.<p>I'm just building out something that I've been wanting for a long time. Opinionated enough to let me move fast like Rails, but leaning on the great work of team Zero so that we don't end up with the scope creep of Meteor. And honestly, it's just really fun to hack on.

Show HN: One – A new React framework unifying web, native and local-first

Hey HN, I'm Nate, the creator of Tamagui.<p>One is a React framework that does two things differently in hopes of simplifying how we build websites and apps:<p>1. It unifies React Native and React web with typed file system routing by making Vite able to serve RN. This lets you share (or diverge) your code in a simpler way for cross-platform apps.<p>2. We've partnered with Zero (<a href="https://zerosync.dev" rel="nofollow">https://zerosync.dev</a>) to make local-first work well. We've been building a solution in One that makes Zero supporting server rendering, without waterfalls, and with seamless server/client handoff.<p>---<p>Honestly - I'm a bit hesitant to post One here.<p>HN has really soured on frontend/frameworks. And I get it. We've collectively complicated the hell out of things.<p>That's why I decided to build One. I loved Rails, it made me as a young developer able to finally realize way more ambitious projects than I'd ever done before. I also liked the promise (not implementation) of Meteor - it felt like the clear future, I guess just a bit too early (and a bit too scope-creeped).<p>I worked at Uniswap and built Tamagui and so spent a lot of time building cross-platform apps that share code. Uniswap is built on Tamagui and I think proves you <i>can</i> make really high quality UX while sharing a lot of code - but it's insanely hard and requires a huge team. My goal with One is to make what is now possible but hard dramatically easier.<p>And I think the path to there goes through local-first, because it makes building super responsive apps much, much simpler, and Zero is the first library to actually pull it off in a way that doesn't bloat your bundle or have very limiting constraints.<p>I happened to live down the street from Aaron, one of the founders of Zero, in our tiny town in Hawaii. We talked a lot about Zero over the last couple years, and I found it really admirable how he consistently chose the "harder but better" path in building it. It really shaped into something incredible, and that convinced me to actually launch One, which at the time was more of an experiment.<p>I can see a lot of potential criticism - do we need yet another framework, this is too shiny and vaporware-y, this is just more complexity and abstraction, etc. Happy to respond to those comments if they come.<p>I'm just building out something that I've been wanting for a long time. Opinionated enough to let me move fast like Rails, but leaning on the great work of team Zero so that we don't end up with the scope creep of Meteor. And honestly, it's just really fun to hack on.

Show HN: TurtleSpaces Web Logo – online 3D Logo implementation

Show HN: RelayBeam – A new way of messaging using Ports

Hi HN! I am developing RelayBeam, to overcome the challenges faced by existing messaging platforms. I've introduced Ports based feature for contextual communication.<p>It organizes conversations based on context through the user-defined ports.<p>I've explained in detail about it with some examples at <a href="https://relaybeam.com/about" rel="nofollow">https://relaybeam.com/about</a><p>Do try and suggest any more features you'd like to use!

Show HN: Quilt – Powerful RAG UI for Document QA

Hey HN! We've just launched Quilt, a robust RAG (Retrieval-Augmented Generation) UI that revolutionizes how you interact with your documents.<p>Key features: - Multi-user setup with private/public document collections - Advanced hybrid RAG pipeline combining full-text & vector search - Smart citations with in-browser PDF preview and highlights - Fully customizable settings and prompts through the UI<p>Making an account is free, no need to even use a strong password: this is only to ensure your documents are separate from the rest.<p>We're keen to hear your thoughts and feedback. What features would you like to see next?

Show HN: I made a super-simple image CDN

Hi HN,<p>MageCDN is a simple and affordable image hosting service I have been working on for the past few weeks. The idea came out of my own frustration with hosting and optimizing images for my blog.<p>While platforms like Imgur make it really simple to upload images, they don't allow you to embed them. Services like Cloudinary, Imagekit exist, but I found them too complex for my needs. Plus, they get really expensive past their free tier.<p>So, I started MageCDN with three simple goals:<p>- pricing should be affordable and scale linearly.<p>- basic image operations (resize, crop, optimize) should be doable within the app.<p>- uploading and getting a link you can use should be fast and hassle-free.<p>Would love to hear what you think!

Show HN: I made a super-simple image CDN

Hi HN,<p>MageCDN is a simple and affordable image hosting service I have been working on for the past few weeks. The idea came out of my own frustration with hosting and optimizing images for my blog.<p>While platforms like Imgur make it really simple to upload images, they don't allow you to embed them. Services like Cloudinary, Imagekit exist, but I found them too complex for my needs. Plus, they get really expensive past their free tier.<p>So, I started MageCDN with three simple goals:<p>- pricing should be affordable and scale linearly.<p>- basic image operations (resize, crop, optimize) should be doable within the app.<p>- uploading and getting a link you can use should be fast and hassle-free.<p>Would love to hear what you think!

Show HN: Flyon UI – Tailwind Components Library

Show HN: Weird Books to Read

Try reading weird books for a change.

Show HN: A Demo for a Strategy Game

This is something that I've been working on on-and-off in my spare time for the last few years. I started in 2020 during Covid trying to do a Mount and Blade style map in UE4, and it grew from there until where it is now - I would just add a feature, then another, until it came together. Since the start of the year I've really been trying to polish it some more.<p>I've got the full thing planned for a Q3 25 release.<p>Github release if you don't have Steam: <a href="https://github.com/joe-gibbs/fall-of-an-empire-release">https://github.com/joe-gibbs/fall-of-an-empire-release</a>

Show HN: A Demo for a Strategy Game

This is something that I've been working on on-and-off in my spare time for the last few years. I started in 2020 during Covid trying to do a Mount and Blade style map in UE4, and it grew from there until where it is now - I would just add a feature, then another, until it came together. Since the start of the year I've really been trying to polish it some more.<p>I've got the full thing planned for a Q3 25 release.<p>Github release if you don't have Steam: <a href="https://github.com/joe-gibbs/fall-of-an-empire-release">https://github.com/joe-gibbs/fall-of-an-empire-release</a>

Show HN: A Demo for a Strategy Game

This is something that I've been working on on-and-off in my spare time for the last few years. I started in 2020 during Covid trying to do a Mount and Blade style map in UE4, and it grew from there until where it is now - I would just add a feature, then another, until it came together. Since the start of the year I've really been trying to polish it some more.<p>I've got the full thing planned for a Q3 25 release.<p>Github release if you don't have Steam: <a href="https://github.com/joe-gibbs/fall-of-an-empire-release">https://github.com/joe-gibbs/fall-of-an-empire-release</a>

Show HN: Kameo – Fault-tolerant async actors built on Tokio

Hi HN,<p>I’m excited to share Kameo, a lightweight Rust library that helps you build fault-tolerant, distributed, and asynchronous actors. If you're working on distributed systems, microservices, or real-time applications, Kameo offers a simple yet powerful API for handling concurrency, panic recovery, and remote messaging between nodes.<p>Key Features:<p>- Async Rust: Each actor runs as a separate Tokio task, making concurrency management simple.<p>- Remote Messaging: Seamlessly send messages to actors across different nodes.<p>- Supervision and Fault Tolerance: Create self-healing systems with actor hierarchies.<p>- Backpressure Support: Supports bounded and unbounded mpsc messaging.<p>I built Kameo because I wanted a more intuitive, scalable solution for distributed Rust applications. I’d love feedback from the HN community and contributions from anyone interested in Rust and actor-based systems.<p>Check out the project on GitHub: <a href="https://github.com/tqwewe/kameo">https://github.com/tqwewe/kameo</a><p>Looking forward to hearing your thoughts!

Show HN: Kameo – Fault-tolerant async actors built on Tokio

Hi HN,<p>I’m excited to share Kameo, a lightweight Rust library that helps you build fault-tolerant, distributed, and asynchronous actors. If you're working on distributed systems, microservices, or real-time applications, Kameo offers a simple yet powerful API for handling concurrency, panic recovery, and remote messaging between nodes.<p>Key Features:<p>- Async Rust: Each actor runs as a separate Tokio task, making concurrency management simple.<p>- Remote Messaging: Seamlessly send messages to actors across different nodes.<p>- Supervision and Fault Tolerance: Create self-healing systems with actor hierarchies.<p>- Backpressure Support: Supports bounded and unbounded mpsc messaging.<p>I built Kameo because I wanted a more intuitive, scalable solution for distributed Rust applications. I’d love feedback from the HN community and contributions from anyone interested in Rust and actor-based systems.<p>Check out the project on GitHub: <a href="https://github.com/tqwewe/kameo">https://github.com/tqwewe/kameo</a><p>Looking forward to hearing your thoughts!

Show HN: Kameo – Fault-tolerant async actors built on Tokio

Hi HN,<p>I’m excited to share Kameo, a lightweight Rust library that helps you build fault-tolerant, distributed, and asynchronous actors. If you're working on distributed systems, microservices, or real-time applications, Kameo offers a simple yet powerful API for handling concurrency, panic recovery, and remote messaging between nodes.<p>Key Features:<p>- Async Rust: Each actor runs as a separate Tokio task, making concurrency management simple.<p>- Remote Messaging: Seamlessly send messages to actors across different nodes.<p>- Supervision and Fault Tolerance: Create self-healing systems with actor hierarchies.<p>- Backpressure Support: Supports bounded and unbounded mpsc messaging.<p>I built Kameo because I wanted a more intuitive, scalable solution for distributed Rust applications. I’d love feedback from the HN community and contributions from anyone interested in Rust and actor-based systems.<p>Check out the project on GitHub: <a href="https://github.com/tqwewe/kameo">https://github.com/tqwewe/kameo</a><p>Looking forward to hearing your thoughts!