codex has an option to expose itself as an MCP. You can also use something like OpenCodex to bring Anthropic models into Codex as any other selectable model.
The reason I did it the way I did was so that I can still use the codex and claude code subscriptions vs paying the API cost. Can you do that via OpenCode?
You can install a different keyboard if you want. I used 3rd party swiping keyboards but ended up using the system one for the last few years because it doesn't bother me.
what was the Nix schism? Did something like systemd happen? or like, Determinate/commercial vs Not? Or more like USA culture wars / code-of-conduct flamers (i vaguely recall some drama around a conference sponsor)?
anyways, i hope there’s a path to some kind of redemption and reconciliation in the future for the community. it sounds like it’s been Bad for years at this point.
maybe wait until you have something to share before Show HN? overall your work seems like a cool thing that i’d like to look at in a few months once there’s more substantial education stuff to read about it.
Your README and docs don’t describe any of the interesting or unique things here. You cover `if` in README but not choreographic programming or perceus. Did i miss some big link?
i poked around in there, under choreographic programming there’s one example of something not in the language as a discarded idea.
if you claim X and Y make us cool and different, then you should document X and Y in your readme. don’t tell me something is the star, and then hide it away. this is baffling to me.
Why would they? The only thing the readme says about RESEARCH.md is "if you want to contribute to the language please read RESEARCH.md". The OP doesn't want to contribute, they want to see an example of choreographic programming. This shouldn't be hard. What is hard is guessing which of the random markdown documents to click to find an example.
sure, but s3 is far easier to buy and also far more reliable than typical distributed systems coordinator stuff like etcd/zookeeper/consul. every major cloud offers it, and there’s several decent open source options.
I haven't deep-dived into celld. Does it requires s3's strong consistency to be correct? or is any s3 api compatible object storage sufficient even if they lack strong consistency guarantee?
the stuff is great when it works but Durable Objects can be quite expensive. whenever i get too excited about em all it takes is a little time trying to price it out to calm me down.
it’s all relative and it really depends on your scale. if your usage fits in the included compute and request count you get for $60/yr it’s absolutely gonna be cheaper. on the other hand, you can run EKS clusters in usw2, use2, apne1, apne2, euc1 for $8600/yr based on my napkin math. to me that does not sound expensive, i work at a company where $8600 is pocket change. but $8600 is much larger than $60/yr for region: earth.
workerd is missing the scheduler - the thing that allows it to operate across nodes. Durable Object storage are just local sqlite databases.
celld is the full distributed system (albeit single tenant). It distributes DOs (cells) across any number of VMs. The databases for each DO are in object storage with RPO=0 guarantee.
bummer this expects NFS; this is all a brand new implementation vs what Cloudflare runs internally in production for DOs? I can’t imagine all your workerds share a single global NFS… What would a more realistic workerd with DO support look like?
Honestly, you wouldn't want to run our internal implementation -- it's far too complicated. Unless you have 100+ datacenters around the world -- then maybe.
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.
reply