SnapFire FSR represents the next generation of Native Full Stack Runtimes that will power the Web.

• Official Website powered by SnapFire FSR: https://snapfirers.com/
• SnapFire FSR: https://snapfirers.com/fsr
• Docs Page Subsite: https://snapfirers.com/fsr/docs
• FSR Github Repo | FSR crates.io

PageSpeed for WWW | PageSpeed for Docs Subsite

Benchmarks - HIGH PERFormance Rendering vs Node's V8 and QuickJS.

You write React and TypeScript. What serves it is a Rust binary with no JavaScript engine inside it.

Not a N...

Sometimes the stars align!

There is no Node.js in this stack. Not at build time, not at request time, not in the container. The build is a Rust binary, the server is a Rust binary, and the thing you deploy is one file with no node_modules next to it.

You still write TypeScript. You write .tsx pages, a load function per route, actions, layouts, middleware, all of it in the shapes you already know from Next.js and Remix. That part is deliberately unremarkable. What is underneath it is not.

This is part of a l...

When I announced Snapfire 0.4.0, the pitch was about the development loop: stop restarting your server every time you touch an .html file. That part hasn't changed, and it still works the same way.

This release is about the engine underneath.

Tera 2 shipped and it isn't a version bump. It's a rewrite. The Rust API changed, the template language changed, and a handful of things that used to fail silently now fail loudly. Snapfire 0.5.0 moves to it.

Today I'm releasing Snapfire 0.5.0.

GitHub Repository: https:/...

Opus 4.8 and Opus 5 have been much better than Gemini Pro hands down. Fable is miles ahead, it can look at Opus output and break out of the mold of limited closed minded thinking. Opus will say these are the 3 choices and Fable will be like nah, you have another choice and Fable is always the better choice over Opus 5. Fable also knows when to stop which further highlights why it is better for planning.

Opus 5 likes to do way more than needed and forget your CLAUDE.md exists, it's annoying. It was a problem ...

rzmq 0.5.24: crates.io | Github - Async, Pure Rust ZeroMQ with Leading Performance on Linux

After some experimenting, I found that io uring was maxed out on a single thread meaning multiple connections could saturate it, so it's been a long time coming, io_uring sharded workers is here! Yes, rzmq's io_uring is no longer one single thread, it's multiple threads now and meets or beats Tokio in throughput.

I knew there was always more throughput on the table because Tokio could do it and I always had a plan to h...

Once in a while a new library comes up and talks how they are high performance, but that's only because they are new and naive. Not many people know about it, so they are allowed to skip on ahead with shortcuts. They've benchmarked and benchmarked, then that effort goes to the wayside as soon as reality catches up. Bugs appear left and right and now they have to value correctness over performance. More people see the old benchmarks and are fooled into thinking, yeah must be fast. Eventually, people do their...

I've been dedicating time to make rzmq much faster more cpu/memory efficient across the board and more correct. 0.5.17 was step up and 0.5.18 was a minor but good performance update

Upcoming version 0.5.19 is shaping up to be a huge performance and correctness update due to fibre bug fixes and efficiency and performance updates (batching) and general rzmq restructuring. Many bugs were found and squashed. Data flows are being simplified and less generalized. io-uring was substantially improved. There's more c...

3.5 Flash is way better than Gemini 3.1 Pro. Unbelievable, it is so fast and accurate. This should be 3.5 Pro while the upcoming 3.5 Pro should be called 3.5 Ultra. It's time to retire the Flash name and move up the barrier. Just Pro and Ultra models.

I used 3.5 Flash to tackle a bug in Fibre where MPMC would leak memory due to the way it handles and doesn't handle adding and removing waiters quickly. The ways that 3.1 Pro and Claude did always came up with a regression in performance 50% - 75% drop in bench...

and I'm getting left behind! No worries though because we have AI Agents that I can query for information about creating AI Agents!

So there's a project that I've always wanted to do with respect to social media management with scheduling. Turns out, with Python, FastAPI, CrewAI, Redis amongst other dependencies, you can easily stitch something together for a bare working AI agent with memory.

I'm excited about this because it is very practical for Hi Stakes Markets Game. I want to spend time on building, not...

Google Play Link

App Store Link

Official Website

Google reviewed it quickly and approved. Apple on the other hand twiddled their thumbs then came back with a rejection based on the idea of needing financial license or whatever. Ridiculous. No matter how many times you mention and put into your terms of service that this a game and not reality nor does it even claim to 100% match reality, they came back with a bull sht excuse to reject

Not once but twice now. This is why the walls for app stores need to be broke...