CLAUDE FOUND THE SEEDS anthropic.com/research/ecdsa…

I think I'm addicted to getting agents to build state machines Every time I see an agent has built a state machine (or even just a reducer) I can feel a huge bump in the robustness And I know that future updates will be trivial and testable Would recommend for frontend

I know what this guy feels very well, but it's not like I can control how the world changes Do you want me to instead lie about where I think things are going or tell you what I think? I prefer we could keep continuing making cool software and people paying for it, but I also studied economics and wonder why would they pay for it if they can pay OpenAI $20/mo instead? I'm not, I'm not the founder of OpenAI or Anthropic, I'm not benefiting from this I'm just telling you what I feel is happening If anything it only disadvantages me because people will cancel my apps too! In transitionary times, it's better to spot the big waves early and adapt, than try ignore it, fight it, because you can't fight nature I'm an eternal optimist but also honest

Unsurprising: simple.wikipedia.org/wiki/Mo…

Selling software is pointless now

Campfire rewrite journey continues. I let the clankers run for a day, go through all the PRs that were submitted, verify the work, merge what was ready, and then ask it to bring all architectural improvements to each implementation. Good old C is now in the lead!

We are proud to introduce our new product, VMPal.com It is a Virtual Machine specifically designed for Apple Silicon and AI Agents. This is our very first release, and it fully supports macOS, Windows, and Linux with GPU acceleration. - Liquid Glass, - GPU Accelerator. - MCP for AI Agent on your Mac or inside the VM.

Anybody have a VS Code fork with all of the extra features and AI stuff removed? I want a minimal editor that doesn't spam me with requests to use a mediocre agent when I just want to quickly look at some code changes.

If you're interested in "how" or "why": the major culprit is that each row in Alacritty has 32 bytes of metadata and each cell is 24 bytes. In Ghostty, every row and cell is represented by exactly 8 byte each. How do we do this? The first major culprit is styles. Alacritty stores the full cell style alongside each cell (foreground, background, underline, etc.). Ghostty stores a 16-bit style ID and de-dupes all styles into a look-aside custom reference-counted hash table. MOST cells are unstyled, and when there are styles MOST styles are shared, and when styles are shared MOST are repeated in a run (multiple cells with the same style in a row). Put this all together, and the tradeoff on compute to access it doesn't even end up being slower. Next, codepoints. Alacritty stores multi-codepoint graphemes (like, Emoji) by having an 8-byte nullable pointer to a `Vec`. This hurts doubly: (1) its almost always null (because multi-codepoint is rare) yet you pay an 8 byte cost on every cell and (2) every multi-codepoint grapheme triggers a heap allocation to make that Vec. Ghostty stores single codepoints inline, but multiple codepoints in a look-aside table. The memory for this table uses a custom bitmap-tracked chunk-allocator (since grapheme frequency follows a measurable curve we calculated by scanning various online texts). The presence of graphemes is marked by a 2-bit content tag in our packed 64-bit cell. To keep the key small in the hash table, its limited to a 16-bit unsigned int that is an offset from a base pointer. Okay, the astute systems programmer will quickly notice there are a lot of 16-bit integers and ask: so this is all limited to a max of ~65K values? Nay. We maintain our grid using a linked list of contiguous ~400KB memory chunks (which themselves are in a memory pool using a custom allocator to speed up alloc/free). Each memory chunk is limited to 2^16. If/when we reach a limit, we move to the next page. In practice, this really doesn't happen except under pathological cases... the important point is we handle it. Lots, lots, lots more details, but thats a 10,000 foot view. These things alone account for ~95% of the difference of our uncompressed vs. Alacritty's uncompressed memory usage. (Theres also a reason why Alacritty's data structures aren't trivially compressable but thats a whole other topic)

Control the ideas, not the code: blog post here antirez.com/news/169