Luckiest

Today's PHP apocalypse is akin to an overdue forest fire for the legacy World Wide Web, that long tail of at least 40M+ websites running PHP. It's the end of an era: the carnage kicking off now plays into a larger ongoing trend for the decline of the human-readable web over the coming years Realistically, despite anyone's best efforts, some uncountably large number of sites are not going to be saved by fire brigades today. These sites are naked and vulnerable and being compromised as we speak. There is no happy ending, only mayhem. This day was always coming. As long ago as 15 years ago, I was warning friends to pick another tech stack for their blogs and their websites, and I'm sure I wasn't alone in doing so. On my part, I felt that the quality of the PHP engine and runtime was a ticking time bomb, and that's only become more evident ever since That bomb has gone off a number of times since, including as critical remote code execution incidents in 2012, 2019, 2024, and now. In total, PHP has amassed some 750+ CVE reports to its name and counting. And as might be expected, the pace of CVEs has picked up this year compared to recent years This crisis is unlikely to be contained. You don't need Mythos access to find problems in the PHP runtime, just point Fable or Astra at it. What we are witnessing is growing strong selection pressure against large hairy legacy code bases in C/C++ Nothing better sells Rust's memory safety and ownership constraints than trying to do without them in a code base like PHP's--at some point even the clanker will begin suggesting that "you know, if I might just rewrite this wee little bit in Rust..." Meanwhile, numerous personal blogs and other cobbler's-children kind of projects are, no doubt, in the process of getting a long overdue migration to static site generators. And another bunch is getting purged off the net altogether, as the easiest and most economical response to getting hacked. Thank goodness for the Wayback Machine!

I finally open sourced the majority of my stack. Mostly at the push of the Artifacts competition deadline. It still needs some TLC on the edges, especially around workflows and git and the clanker UI's... All that aside! Here is Oyster. Your OS for agents, and everything else. For normies its a Hermes, Openclaw, Bot, Dot like thing. Its potential is much more than that though. Ryan Dahl is talking about distributed OS's over durable objects, you all should pay attention and learn what he is talking about. Oyster is my attempt at one of those. It uses Cloudflare's "Computer" package as a machine abstraction. This can be a DO on their platform, with their containers, the way they make so easy. I have also tested it extensively on Hetzner with Celld. By building apps over this computer interface you can do things like give every agent its own computer, then build apps that hook into these computers for media gen, workflows, git, file editing, whatever you want. This tweet is long enough, Ill fire off some more specific ones shortly. I will be talking about it a lot today, and the rest of the year probably. Hope its not annoying. github.com/fungi-computer/oy…