Is this using WebContainers? Or is it just very similar?
The HN discussion about StackBlitz focused on the problem that it would only work in Chrome… I assume that's true here as well? (Due to lack of the File System Access API?) https://news.ycombinator.com/item?id=27223012
> Faster than local dev: Because it runs entirely within the browser, server responses have less latency than localhost.
Next.js Live seems very impressive, but this marketing line is scaring me off. It’s hard to imagine that running your app in webassembly within the browser has a measurable reduction in latency vs running on localhost. If anything, I would expect it to be slightly higher because of the overhead of interpreting/compiling wasm, and the slight performance hit of wasm vs native code.
It’s because in normal localhost you have to spin up a server in another process that serves your JS. With this there’s no server serving your JS. It’s right there in the browser already. That’s what they mean.
I understand, but it is not obvious this provides a performance benefit which outweighs the potentials slowdowns I mentioned above. I am concerned about the trend of JavaScript tools advertising how they are “blazing fast” without any benchmarks or serious technical analysis.
Hi Aaron. First time learning about replicache. Headed over to the website and the documentation on the server portion seems to be a lot of TODO links. Before diving into Live, which looks very cool, I guess I'd want to know more about what the server side implementation looks like. I could see using this for a golang backend that I have to sync data with. Thanks.
It's an opinionated react framework with dev tools to make it easy to:
- render on the client, server (lambda function), or at build time
- easily create lambda function at edge to act as API endpoints
the same ideas have been ported to Vue and Svelte equivalents.
While Next.js Live is framework specific (redesigning the Next.js dev server), the collaboration features will eventually be rolled out for the entire Vercel platform!
The keystrokes edit the local in-memory state and are synchronized in batches to the server and other collaborators. Learn more here: https://replicache.dev/
I still haven’t seen anyone explain how this code gets deployed to the shareable URL though. Is it being pushed to the Vercel edge network when you run next dev? What is actually happening when you use this on-page code editor? Where are those code changes being persisted to?
I went to see the Vercel fork because I was curious what sorts of modifications you’ve made, but i couldn’t find it. Are you planning on publishing your changes? Can you say a little about what they are?
Clarification – it's actually a fork on the entire VSCode, not just Monaco. This allowed us to add features like locking the editor when others are editing the same file.
https://blog.stackblitz.com/posts/introducing-webcontainers/
Is this using WebContainers? Or is it just very similar?
The HN discussion about StackBlitz focused on the problem that it would only work in Chrome… I assume that's true here as well? (Due to lack of the File System Access API?) https://news.ycombinator.com/item?id=27223012