it's shocking that software engineering has transitioned to 100% AI written in such a short time.
it's more shocking that somehow we, the SWEs, are all just continuing on as if nothing happened. It writes C++ better than I ever could, but the problem of making sure it works didn't magically disappear. we are just shipping enormously more volume at higher quality.
This isn't your typical acquisition blog post. I'm really excited not just that @rough__sea, @piscisaureus, and friends are joining, but also what they plan to work on: Making workerd a first-class, self-hostable open source runtime. Read for more:
The team behind @Deno_Land, including @rough__sea (he knows a bit about Node.js), is joining @Cloudflare.
They’ll help make Workers better for Node.js developers and advance workerd as a core primitive for what comes next.
reflecting on 1920s images of people working on massive generators for the electrification of the modern world makes me realize that the past was wildly futuristic too
rust never was the defacto language for agents and will not be. i love rust - it’s my primary language - but i work on runtimes and platforms
application code belongs in the default language - JavaScript (or its extension TS)
Rust no longer the defacto best language for agents
Compile times are too long, I'm always finding myself bottlenecked by time not intelligence
And the agents have gotten really at doing manual memory management now
Wrote an article walking through how we use deterministic simulation testing (DST) in celld to find bugs that would otherwise be hard to discover, including a race condition caused by an unexpected execution order
#celld#
@rough__sea@meso Having celld absolutely makes me more willing to build apps that plug directly into the Durable Objects and workers APIs. It's going to increase my usage of both celld for on-prem deployments while also increasing my willingness to deploy more to CloudFlare.
i feel like people do not grok how important celld is.
it's scalable applications of arbitrary complexity. the only dependency is s3.
once you see it, you'll realize there's no point to traditional javascript runtimes in serving applications - only for build processes (eg bundling) and scripting.
the networking and scaleability are deeply rooted not only in the distributed runtime (celld), but in the programming model itself (largely kenton's design)
I wasn't quite sure when I started celld how well this could be made to work, but we've been running it in bigger capacities and getting user reports over the last months. Actually handles load surprisingly well. (any experience in the comments to share?)
because the programming model does not expose the underlying linux system, you can actually think of celld as a distributed operating system - running in user space of linux. it only runs one program / doesn't support multi-tenant, but it has system services like an operating system. it's all about networking - i like to think of it as the practical modern version of plan9 or even erlang beam.
Disagree
just as high level languages help us code better - there's less to think about, it will be the same for AI. Why reach for ASM when you can use Rust - there's so much more that can go wrong. By this logic AI will also forego testing because they have so much intelligence to just reason through it.