31–40 of 56 posts
i would prefer a thing that was more self-contained, not dependent on a black box service layer underneath.
much apologies if i just have a poor understanding.
Well that couldn't have been any more timely. Did they know? Were they keeping this in a back pocket for the time? CloudFlare OS: https://blog.cloudflare.com/cloudflare-os/ https://news.ycombinator.com/item?id=49182996 And yes, celld is isolates! The very lightweight within v8 isolation boundary. Hence the "very low idle cost". The deno team rolled their own new runtime! This one without deno_core! Shout out to this…
I'm probably missing your point, but aren't wasm memories achieving exactly this? Just an example from wasmtime: https://docs.wasmtime.dev/examples-multimemory.html
Could someone explain to me in practice how one would use these to do… a thing? Like a straightforward use case? Having trouble figuring out what these are for
Could someone explain to me in practice how one would use these to do… a thing? Like a straightforward use case? Having trouble figuring out what these are for
More practical example (serverless WebSockets) https://youtu.be/FgWVoryZ8PU
Wonder if this will become common practice from now on ? > Pull requests are disabled. Coding agents make it too easy to send a large, > low-context change that costs maintainers more time than it saves. > Thoughtful contributions are welcome; please understand the code, > keep the patch focused, and respect the review time you are asking for. > > Send a git format-patch attachment to ...
Wonder if this will become common practice from now on ? > Pull requests are disabled. Coding agents make it too easy to send a large, > low-context change that costs maintainers more time than it saves. > Thoughtful contributions are welcome; please understand the code, > keep the patch focused, and respect the review time you are asking for. > > Send a git format-patch attachment to ...
Wonder if this will become common practice from now on ? > Pull requests are disabled. Coding agents make it too easy to send a large, > low-context change that costs maintainers more time than it saves. > Thoughtful contributions are welcome; please understand the code, > keep the patch focused, and respect the review time you are asking for. > > Send a git format-patch attachment to ...
time to bring back the dev email distribution list
Earlier quoted context omitted.
You beat us to it! Been meaning to land this but got distracted. https://github.com/cloudflare/workerd/pull/6780 But honestly I love that there are multiple implementations now.
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? ah well, we have celld!