4 ms·
That's an interesting idea to generate javascript and execute it client side rather than server side. I'm sure that saves a ton of money for Anthropic not by no
by animal_spirits 2y ago
That's an interesting idea to generate javascript and execute it client side rather than server side. I'm sure that saves a ton of money for Anthropic not by not having to spin up a server for each execution.
- stanleydrew 2y agoAlso means you're not having to do a bunch of isolation work to make the server-side execution environment safe.
- Me1000 2y agoThis is the real value here. Keeping a secure environment to run untrusted code along side user data is a real liability for them. It's not their core competency either, so they can just lean on browser sandboxing and not worry about it.
- cruffle_duffle 2y agoHow is doing it server side a different challenge than something like google collab or any of those Jupyter notebook type services?
- trillic 2y agoGoogle Collab are all individual VMs. It seems Anthropic doesn’t want to be in the “host a VM for every single user” business.
- donavanm 2y agoShared resources and multitenancy are how you get efficiency and density. Those are at direct odds with strict security boundaries. IME you need hardware supported virtualization for consistent security boundary of arbitrary compute. Linux namespaces (“containers”) and language runtime isolation are not it for critical workloads, see some of the early aws nitro/firecracker works for more details. I _assume_ the cases you mentioned may be more constrained, or actually backed by VM partitions per customer.
- deleted 2y ago[deleted]
- qeternity 2y agoThe cost savings for this are going to be a rounding error. I imagine this is a broader push to be able to have Claude pilot your browser (and other applications) in the future. This is the right way to go about it versus having a headless agent: users can be in the loop and you can bootstrap and existing environment. Otoh it’s going to be a security nightmare.
- deleted 2y ago[deleted]
- rajnathani 2y agoThe cost-savings would actually be significant. Spinning up a sandboxed container/VM or chroot jail a thousand times a month for a user paying a $20/month, when you already as a company have huge GPU bills on the training and inference side and NRE costs, would be gaping.
- qeternity 2y agoI really really don't think you understand how cheap it would be to spin up a node.js env a thousand times a month in a container. Let's be really really conservative and say that each invocation takes 30s of CPU time, resulting in 30,000 CPU seconds per month. Let's say that CPU cores can be had for $10/mo. We are talking about 10 cents per user per month. And in reality, this is still probably over an order of magnitude too high. You are literally talking fractions of a cent in reality.
- rajnathani 2y agoYes actually it would be cheaper if one pre-provisions VMs. Albeit, to ensure sufficient provisioned capacity that one would have to slightly over-provision here, and for a coding power-user that it would be almost $2-3 cloud costs per month excluding the software engineering costs of maintaining this fleet of servers and scheduling jobs on it.
- qeternity 2y ago
- bhl 2y agoMakes a lot of sense given they released Artifacts previously, which let you build simple web apps. The browser nowadays can be a web dev environment with nodebox and webcontainers; and JavaScript is the default language there. Allows you to build experiences like interactive charts easier.