20,211 karma · joined December 12, 2011
Also created: capnproto.org, sandstorm.io, lanparty.house
TBH I'm pretty confused why anyone uses "for you". For me at least, any time I accidentally wander over to that feed, the stuff it shows me is just dumb... not even political necessarily, just dumb clickbaity shit that insults my intelligence.
The only time I ever see hyper-political stuff is if I peek into the replies to a prominent politician. Highly recommend never doing that.
EDIT: Oops, I think I misinterpreted, you meant to compare Jack vs. Elon as CEOs of Twitter itself.
When choosing a social network, probably the top priority for most people is where the people they want to talk to are.
If CEO antics were the thing that mattered, I would certainly choose Bluesky over X. But the reality is the tech community -- at least, the part of it I want to interact with -- is mostly on X. Many of us tried to switch to Bluesky for a bit but ironically got pushed back to X due to Bluesky culture being hostile to tech and especially hostile to AI. I'd post the same non-political tech thing on X and Bluesky and get lots of interesting feedback on X while getting screamed at on Bluesky, so I stopped posting on Bluesky.
Would love for this to change but it's a hard problem.
There is a loyal community of enthusiasts trying to keep it alive, but realistically not a lot of progress has been made. (Though, AI has helped them make more progress lately.)
But the original creator of Sandstorm (me) did indeed abandon it long ago (sorry).
More here: https://sandstorm.io/news/2024-01-14-move-to-sandstorm-org
(shameless plug)
But Cloudflare OS also supports a concept of "blueprints", where, once you've built your app, you create a "blueprint" (a copy of the code) and share it with others, from which they can create their own instances of the app. So it is still very much about sharing apps and running other people's apps, and the sandbox makes this safe and compliant even if you're not sure the app developer knows what they're doing.
Or at least, ideally. Unfortunately, content-security-policy today has a few exotic holes. WebRTC, for instance, cannot be blocked; the standard simply doesn't cover it.
So it's not suitable as a sandbox against malicious code trying to leak data by any means possible. Instead it's protection against the AI doing something stupid, perhaps prompted by a user who doesn't know better.
(We would love to get those CSP holes plugged, though...)
I am the lead engineer on Cloudflare OS (and Cloudflare Workers).
I am also the creator of Sandstorm.io.
And I'm the one calling it a successor. Wasn't some marketing decision -- that's directly from me.
Honestly really interested to know why you feel this isn't accurate.
FWIW, I didn't choose the name Cloudflare OS -- but I did frequently describe Sandstorm as being an OS, back in the day. Sure, it layers on top of Linux, but it's an environment where you install apps and run them, with the platform managing the execution environment, permissions, resource management, etc. That's sort of what an OS does. Cloudflare OS does all that as well.
I disagree. In fact, I find people who think of themselves as highly rational seem to be particularly prone to rationalization. Because being rational is integral to their whole identity, they are much more eager to accept their own rationalizations as sound and resist admitting that they are guided by instinct.
What makes you so sure your own brain doesn't work the same way?
We often make a decision based on a gut feeling, and then backfill a logical reason supporting our feeling, without even realizing we're doing it -- rationalization.
But also, the Cloudflare Workers Runtime is open source, so you could deploy it or your own machines, too, if you want:
I think I missed that and assumed it wasn't because it performed similarly to the dense models. Interesting!
I'm finding that the Mixture-of-Experts (MoE) models (Qwen 3.6-35B, and Nemotron 3.5 Lightning) are, well, terrible at this. They just couldn't get the job done at all. Went way off the rails. They are really fast though!
Whereas ~30B dense models (not MoE) are pretty decent. I tried Muse Glimmer, Gemma 4-31B, Qwen 3.6-27B, and Laguna XS[0]. They were all able to build a working collaborative whiteboard app, without any guidance (other than feeding back error logs to the model). I also asked each to then draw a monkey by calling the API of the whiteboard it has just built. Laguna drew random scribbles but the rest all managed to produce something monkey-like.
(Frontier models in comparison will write the app in one shot with no errors at all.)
Note that both Qwen 3.6 and Gemma 4 each have both MoE and dense variants. I find this very confusing, because e.g. ollama's model index typically only distinguishes variants by their size, but MoE vs. dense makes a huge difference in how they actually perform. IMO they should use a suffix, like Qwen 3.6-moe vs. Qwen 3.6-dense, or maybe Qwen 3.6-fast vs. Qwen 3.6-smart...
[0] EDIT: Turns out Laguna XS is MoE, I misunderstood. It performed similarly to the dense models. But maybe this explains why it couldn't write code and think about monkey shapes at the same time!
What would we have done differently in that case?
Didn't need it yet on day one. :)
We aren't that clever about naming at Cloudflare.
Do you know how we named Wrangler, our local dev tool for Workers?
Literally, the person that created it said: "I named this Wrangler because I wanted to give it a name so dumb that we definitely won't release it under that name and will come up with something better."
We didn't come up with something better later.
Honestly Cloudflare OS is kinda same thing. We brainstormed names last week trying to come up with something better but nobody could agree on anything so it just went out as Cloudflare OS, which is what we'd been calling it internally for no particularly good reason.
But I'm certainly not claiming that this alone is sufficient to comply with regulations. I have no idea.
The goal of this new design is to scale to a cluster while being operationally very easy to set up. Ideal for self-hosting.
NFSv4 is an easy first step, convenient because it's broadly understood, has many implementations, and requires no client libraries. I could imagine a follow-up to support LiteFS instead of NFS could make a lot of sense, though it'll get more complicated.
But yes, celld is definitely ahead of us here. No doubt about that.
If we open sourced Cloudflare's production scheduler, nobody would be able to use it because it is explicitly designed for HUGE, globe-spanning scale. Well, nobody except our direct competitors.
But the goal with workerd is actually that it should be pretty easy to run, about as easy as Node. Stateless workloads should scale trivially (just add more instances and load balance). For Durable Objects (statefull), currently it doesn't scale well at all, but I'm working on changes[0] so that it scales nicely across a cluster. I intentionally chose a design here that is operationally easy to set up. (Basically: just connect all the nodes to NFSv4.)