QuiiBz

Sandpack is made by CodeSandbox, not StackBlitz: https://github.com/codesandbox/sandpack

They recently raised $50M in a Series B: https://www.warp.dev/blog/warp-drive-series-b

Cicada looks very promising, congrats. I'm wondering why you choose to use Fly.io for the CI/CD runners, instead of using VPS / baremetal servers that are a lot cheaper? Do you need the edge features that Fly.io offers?

Thanks for your detailed answer.

> release workflows

Looking forward for this, especially if that also means auto-publishing of NPM packages, Rust crates, etc.

Congrats on the launch! I've been following Moon since a few months, seems like an interesting project.

Could you explain why any existing project using Turborepo/Nx should switch to Moonrepo? What are the advantages and disadvantages? The support for multiple languages seems like a big advantage.

I'm building Lagon, an open-source [1] runtime and platform that allows developers to run TypeScript and JavaScript serverless functions at the Edge, close to users. The runtime uses V8 Isolates and is written from scratch using Rust and rusty_v8 [2], Deno's Rust bindings for V8.

[1] https://github.com/lagonapp/lagon

[2] https://github.com/denoland/rusty_v8

> We’re excited to integrate Gatsby’s cloud innovations into the Netlify platform

I feel like the acquisition is more focused on Gatsby Cloud than Gatsby (the framework).

> How do we know this?

Looking at the source code [0] for Deno HTTP server, they spawn at least one thread for the server to listen and handle requests, before they are sent through a MPSC channel to the thread running the Isolate.

[0]: https://github.com/denoland/deno/blob/07213dec94398aab687afd...

Absolutely love the design.

I wonder what can this be used for?

It's back up for me (EU, France), was down for about ~30 minutes.

I wonder why the headline and other gradient title are images. Why not a text with linear-gradient and background-clip?

Great news! Feel free to DM me on Twitter (@tomlienard) if you want to chat about this, as I also want to support Next.js in the future for my runtime.

I wonder if we can build a Next.js app with this new `edge-runtime` mode, and host it on any platform that supports `edge-runtime` [0] APIs (like Cloudflare Workers (I think Vercel uses it?) and Deno Deploy).

If yes, that's truly amazing. It'll empower more and more people to run stuff at the Edge. I'm also working on an open-source alternative to the above offers [1], so I would love to be able to run and support Next.js on it.

edit: formatting

[0]: https://edge-runtime.vercel.app/

[1]: https://github.com/lagonapp/serverless

I don't understand why there's two apps, name and domains (doing the same thing?), one redirecting to the other.

Is your startup named OpsFlow (previously digger.dev)? Or is OpsFlow a new product home digger?

> initially

Does that mean you want to roll out your own runtime in the future?

I would love to see more in-depth explanations about Oxygen [0]. I'm currently creating a similar runtime [1] based on V8 Isolates so that would be interesting to compare.

[0]: https://shopify.dev/custom-storefronts/oxygen [1]: https://github.com/lagonapp/serverless/

For now, each process runs many isolates - but a single server run many processes. Cloudflare have implemented a similar mechanism [1]:

> Workers are distributed among cordons by assigning each worker a level of trust and separating low-trusted workers from those we trust more highly. As one example of this in operation: a customer who signs up for our free plan will not be scheduled in the same process as an enterprise customer. This provides some defense-in-depth in the case a zero-day security vulnerability is found in V8.

[1] https://blog.cloudflare.com/mitigating-spectre-and-other-sec...

Can you give a link to this? Cloudflare (Workers) and Deno (Deploy) both uses v8 isolates for their runtimes, with I believe some significant clients running production code (huge clients like Vercel and Supabase use these solutions)

Edit:

> If you execute untrusted JavaScript and WebAssembly code in a separate process from any sensitive data, the potential impact of SSCA is greatly reduced. Through process isolation, SSCA attacks are only able to observe data that is sandboxed inside the same process along with the executing code, and not data from other processes.

I do run isolates in separate processes to prevent security issues, even if that may not be enough. Still an early prototype for now.

I’m currently building a FaaS runtime using v8 isolates, which I hope to open-source soon. That’s actually not that hard since isolates are, isolated from each other.

Performance-wise, it’s also very promising. For a simple hello world, the « cold start » (which is mostly compile time) is around 10ms, and on subsequent requests it runs in 1ms.

The blogpost is from two years ago.