this is my personal singularity moment this post may sound like a paid ad. I only wish. I'm concerned, more so than happy. the world is changing, and, among the scenarios where AI goes terribly wrong, inequality is the most realistic, yet, the one Anthropic seems to be the least concerned about. I'm glad OpenAI is taking the opposite stance: *personal AGI for everyone*. I think this is a commendable position in the times we live. but who am I in the queue of the bread? anyway, Fable is here, so I'll just report my first-hour experience first of all, all my pet prompts are solved. → λ-calculus puzzles → bug questions → one-shot apps all are trivial to it. I don't have anything harder other than my ongoing work so, in the last several days, I've been toying with HVM5, a new interaction net evaluator with a faster loop. after writing the first version, I left 32 GPT-5 agents working for ~20 hours each. this resulted in up to 2x speedups, but the file size increased by 2-fold and quality decreased significantly. I then simplified the whole thing into an even simpler core, and left Opus 4.8 and GPT 5.5 optimizing it for 8 hours. Opus got a legit 6% - 34% speedup in most benches. GPT got better results, but, sadly, an unusable file. I then asked Fable to optimize it. 2 hours later, it landed a 1770% speedup in one case, 100% in other 4, and 22% in average. yes, in 2 hours it outperformed me, opus 4.8 and a swarm of gpt 5.5 agents, by one order of magnitude. that could not possibly be legit. "it must be hardcoding the benchmarks" (GPT trauma). so I read its explanation and what it did was, indeed, the most high impact optimization one could try first. seems like HVM5 was wasting a lot of time garbage-collecting unused branches of pattern-match nodes. I had optimized that for static mats, but not for dynamic mats. skill issue. Fable figured how to do it for these, resulting in a massive speedup in some benches but wait, is that *correct*? I'm not sure yet, it is credible, but this is the kind of thing that is very easy to get wrong on interaction nets. the problem is, when I was ready to start auditing Fable's solution so I could tell whether it was buggy or legit, it interrupted me to tell me it had found a massive bug on the code *I* had written. ... wait, what? so... for garbage collection purposes, I stored a bit on lambda term pointers that meant "the variable bound by this lambda has been freed, so, its lambda must free whatever argument it is applied to". that's fine. yet, on duplicator nodes, I also used the same bit to mean "one of the duplicated variables was freed, so, treat this dup as a passthrough no-op". so, if a lambda entered a duplicator, it would mistake the lambda's collection bit for its own, resulting in corrupted interaction! that's a mouthful, why I'm writing this? just so you can appreciate the sheer absurdity of what just happened. I didn't ask it to find bugs. I asked it for an optimization. and even if I did ask it to find bugs, this bug is so astonishingly subtle and specific, identifying it takes mastering the domain to an extent that it beyond even me. I'd easily need hours or days to fix it, *if* I ever came across it. chances are it would just go unnoticed. and Fable found it and fixed it like it was nothing, while it was busy adding a 17x speedup to a file that neither I, nor Opus 4.8, nor a fleet of GPT 5.5 managed to barely make 2x faster. oh and there is also another tab where it is also ripping through Bend's codebase and finishing everything I had to do I don't know what to say anymore this isn't about Anthropic or OpenAI, this is about our collective future as a species. the world is changing, and we need to be aware of it, and discuss how to handle this change. receipt below . . .

Wuque Studio x Alexotos 6th Anniversary giveaway! 🏆Freya keyboard (Without keycaps and switches). How to participate: 🖤 Follow @otosalex @Wuquestudi24300 🖤 Like & Repost 🖤 Tag a friend 🏆 1 Winners 🌎 Open Worldwide ⌛️ Runs for 1 Week Winners: 1 winner gets the Freya kit Message from wuque: We're giving back to all our loyal old customers as we celebrate this special milestone. Check out exclusive offers here: meletrix.com/

Sigh... I think it’s time to address some recent controversy. For the past few months, I've been experimenting with AI coding agents to familiarize myself with this new programming paradigm. The result of that experiment is the samloader-rs project. I chose "Samsung firmware downloading and flashing" because the problem space is small and self-contained compared to something like Magisk. It’s also genuinely useful to me; none of the existing tools fit my exact needs. Regardless of what you think of the codebase, actual engineering work went into this. I reverse-engineered the LZ4 data transmission by myself because I didn’t know the brokkr-flash project existed at the time. With no code or docs to reference, I pulled out Ghidra for the first time. I’m the first to admit I’m an assembly noob, so my approach definitely has flaws. And yes—99% of the code in samloader-rs was written by AI. I have never tried to hide this! But every single commit was reviewed, tested, and tightly guided by me. I drove the development and purposely delegated only the "coding" part to the agents. The Samsung firmware scene is new to me, and I used AI to catch up to speed so I could make tangible progress. It’s not perfect; AI cannot replace years of human research. However, seeing people use my learning curve and my use of AI to completely discredit my contribution to this project—and worse, use it to discredit my legacy on Magisk—is incredibly disheartening. I’m just trying to learn, build, and share in an area completely new to me. I built Magisk on the shoulders of many existing open-source efforts, and today, forks and derivative projects stemming from it are flourishing. To me, open source has always been about learning. It’s deeply saddening to feel discouraged from doing exactly that, simply because I used AI as a tool. Balancing a full-time job and starting a new family in a foreign country means real life takes a toll, and free time is incredibly sparse. Without these new AI tools, dedicating the time and effort required to dive into a brand-new area of interest would be nearly impossible. To be honest, I kinda regret open-sourcing samloader-rs. It exposed my lack of knowledge on a new topic and thrust me right into the middle of the AI coding controversy. 🫤

I GOT THE DOMAIN! I FINALLY GOT IT!!!!!!!!!!1 🥳🎉 Paint​.NET is now at paint.net! Well, it will be just as soon as I push all the buttons to migrate content and set up redirects from getpaint​.net etc. For now it's just a "hey go here" redirect page.

Haters mad

RT @uwukko: A fresh Brave install in 2026: sponsored ad wallpapers on new tab page by default (opt out). Brave VPN, News, Talk, Leo (AI), R…

Europeans travelling to the USA

Last year, miHoYo copied my puzzle game Ouros in Zenless Zone Zero. Because they are a recognized, billion-dollar studio and my game isn't well known, some people are now assuming that their version is the original, and mine is the clone. I hope this video clears that up.

Girlies in tech, I’ve invented a new hobby for us! ‘Crocheting with Computers’

PLEASEEE BRING BACK TABS V2 OR AT THE VERY LEAST SOME FORM OF AN (OPTIONAL) ONE-HANDED FRIENDLY UI

a sequence of words that will never be said again

디자이너 포폴 허들 정말 높다

Unfortunately, I don't use Zig now. Every 1.5-5x human DX productivity boost from Zig features is eclipsed by the 100x boost from coding agents writing Rust: Allocator interface: This is my favorite Zig feature, you feel so galaxy brain using a specialized allocator to optimize a code path (e.g. arena, stack fallback etc). The problem in Rust used to be that there was no Allocator interface equivalent and if you wanted a Vec<T> that used a custom allocator you literally had to copy paste the std version and modify it to use it (this is what Bumpalo did, look at the source). For a long while now there has been an Allocator trait in nightly, and it seems to be good now. Because it is a trait it is static dispatch, vs Zig's which is based on a vtable. Unlike Zig there isn't a community-wide convention of designing data structures to be parametric based on the allocator, but AI changes the game and makes it trivially to copy paste code and change that. I find it works well enough for my use-case. Arbitrary bit width integers packed structs: Another beloved Zig feature of mine. It makes it so easy to do DOD-style CPU cache optimizations and stuff like tagged pointers, NaN boxing, etc. and even made bitflags really easy to make. You could always do this in Rust or any systems programming language but it was really ugly/unergonomic. The least worst option was using some crate like bitfield/bitflags which both rely on proc macro magic to work. Now, with coding agents I literally do not care how annoying it is to write the code by hand. Comptime: This is Zig's flashiest feature, no other programming language except maybe for obscure dependent-types langs have compile time evaluation as nice as Zig's. I thought I would miss it a lot, but I actually don't. For me, 95% of comptime usage is to create Zig's version of generic data structures with parametric types. Rust has a better designed type system IMO (see next section). In the remaining 5% of cases, not having comptime sucks. The only reliable way to reach an equivalent is through codegen. I'm making a game right now, and I have hardcoded hitbox geometry data generated from a tool that I want to bake into a data structure. Without comptime, I have to get Claude to write a script that generates the Rust file. However, I don't find myself needing compile time evaluation that much anyway. Rust's type system: I think I'd rather trade having comptime for Rust's better-designed type system, especially for bounded polymorphism (traits/typeclasses). Trying to do the equivalent in Zig is a nightmare. Also, I think that Rust's type system allows you to enforce more variants and prevent coding agents from making common mistakes. In my game I use the euclid crate which essentially allows you to not mix up coordinate spaces (very common problem in graphics programming) by creating specialized types for each coordinate space (e.g. Point<Screen> or Point<World>) Not having to deal with memory issues: With coding agents allowing 100x more code to be written, this also means you need to scrutinize 100x more Zig code for memory issues. Without formal verification, the surface area of the search space to enumerate to find bugs is just so much larger now. With the magnitude of code being generated now, Rust is even more attractive. Rust's tradeoff was always that it hinders developer productivity especially if you are unfamiliar with borrow checker, but this simply does not matter with coding agents anymore. And if you do use unsafe in Rust there's tools like miri which you can have the coding agent run the code against to make sure it doesn't cause UB or isn't violating Rust's aliasing rules when it comes to unsafe. I still miss writing Zig and find it to be a great language but I like Rust more and coding agents work with better with it.

RT @f_lynyrd: Panicked thinking I had forgotten mothers day then remembered that I'm British and had already forgotten it earlier in the ye…

announcing Marc Andreessen Egg Game - a game where you draw on eggs to make them look like Marc

I’m looking for the first full-time developer for neal.fun! You’d work with me on making new web projects and games for the site. Preferably in nyc If anyone is interested or has leads dm me or email hi@neal.fun!

More pics, looks incredible in person. First time it had lights in its 123 year history!

YOOO WIRE TENSION LFG it was a lot simpler than I wanted to make it, but it's working. Last technical hurdle verified. Let's cut 4-axis WEDM on desktop!!

Tech companies are basically lying to you: - They compare their new products to ones released MANY years ago (to make it as confusing as possible to figure out how much has actually changed this time) - They invent new specs that mean absolutely nothing (like how much zoom their phone cameras can do) - They write “up to” just before telling you how much their new product has improved by (so you can’t sue them when you don’t get those numbers) And a LOT more So, I decided it was time to break it down with @MKBHD on YouTube - video live now