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.
Awww, I was hoping GP would respond before they realized who they were responding to, could have been a classic exchange in the vein of https://news.ycombinator.com/item?id=35079
I didn't know about Sandstorm, but you might have an easier way conveying this by stating "Created and inspired by Sandstorm.io and its creator." I think the "inspired by" remark is easier for most to understand, and it sells it more if you point out that you're its author.
As for the name, yeah, not really a fan as I noted above.
FWIW I saw the original posts, knew who wrote them, and know that Cloudflare OS is open source. It's because Sandstorm is about running anyone's apps, while where you introduce it you say this:
> the AI cannot introduce a significant security bug
The AI-authored apps aspect is obviously something that Sandstorm didn't have.
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.
Seems to be mixing up linting with code review - though this does lint only the changes which is an option (I prefer to lint the whole codebase though)
Eh, the "real food" of Jamie Oliver and Michael Pollan (shop the peripheries) and such isn't very health promoting. So I'll pass and keep eating a mix of fresh food and cheap food that keeps for a long time like legumes. Kthxbai.
To Michael Pollan it seems they aren't worth mentioning right in the first breath when talking about real food, but perhaps an afterthought. "Shop the peripheries" causes them to be lumped in with potato chips and oreos and other stuff that aren't in the peripheries of a supermarket. I don't accept the same real food dichotomy that they do.
Beans are a direct product of plants. I don’t know what you are on about, but I’m sure even the celebrities you take so much stock in consider them “real food”, too. I wouldn’t know, because I have no idea what you’re ranting about.
They talk so much about freshness. That is an indirect and unnecessary and probably unintentional dig at dry beans, grains, seeds, nuts, etc. While I can entertain the idea that they're more reasonable in their diets this makes them bad nutrition communicators.
I seem to remember TamperMonkey being on there but not ViolentMonkey, which I didn't agree with. However, I see neither of them on there. Both are available but not recommended. I wonder what is going on with that.
I see GP's point tho. The original Greacemonkey was open-sourced. Tampermonkey was the successor and is proprietary. Violentmonkey came to fix that. I wouldn't be surprised if Mozilla rejected TM because of not being OS and rejected VM because of lack of popularity
I get what you mean, and it'd be cool if "Recommended" was only for FOSS, but I don't think that ever been the case? Probably lots of the "Recommended" extensions are proprietary, from https://addons.mozilla.org/en-US/firefox/search/?promoted=re... you don't get far before hitting one, the 3rd extension already is proprietary out of those, surely more.
I suspect they no longer recommend either because either can download/execute scripts that Mozilla can't review, and the recommended extensions are reviewed, so they don't want to give users the wrong impression.
If it were intended to be a direct alternative for the biggest use case, I think it would be more like Cloudflare Workers and Durable Objects. However, I think it's an alternative for a lot of uses of those two things. For a lot of uses of them, likely most uses, they are overkill.
So where it's overkill, this is where Celld is a good fit. It's a 100% open play, despite mentioning three hosted APIs: S3, Cloudflare Workers, and Durable Objects. The thing is, that Deno tried making similar ones. Deno Deploy is analagous to S3, and Deno KV is analagous to Durable Objects. However, with Celld the only dependencies are being able to run a binary and some S3-compatible storage. Cloudflare provides S3 compatible storage, but this README doesn't mention that, except in an example. Perhaps Ryan is leaving the door open for Deno to be acquired by Cloudflare.
There is also qm with smol machines. I found this out the long way, by looking at the contributors to qm at https://github.com/yc-software/qm where I found BinSquare, the founder of smol machines. Then I found a tweet about a public instance of it where I could try out having it code something agentically - I'm in the replies here: https://x.com/binsquares/status/2083305704274976819
I guess the lock-in is to Cloudflare Workers, which is limited to JavaScript. I would in fact look into projects that are built around MicroVMs and WebAssembly. It seems Buzz would be happy to use smolmachines, or whatever. You'd have to roll your own permission system, but smolmachines would at least take care of being able to use stuff within an app, by offering persistent, portable containers.
Actually I think now I can finally say why this sandstorm.io with Cloudflare OS has lock-in. The promise is "you can pretty much go wild" and that you can hand it off to non-technical people to do that. Much as you squint, there is not a sophisticated access control system available to self-hosted users. There's a framework for building a sophisticated access control system, but that isn't the same as having something open source that you can self-host and let non technical users go wild.
However, this is cool. I just agree with you that Buzz sounds more interesting to me as someone who was into Sandstorm.
Ah, that changes the amount of work and the reward in the equation for attempting to self-host Cloudflare OS. And I knew that I could run WebAssembly manually inside of JavaScript, but it seems to be runnable directly too. What would help me to know further is how Cloudflare OS integrates its access control in that open source project, and if it is conveniently available to WebAssembly, Python, or Rust workers.
reply