In case of REPL, you send STDIN to websocket and get STDOUT as response. All code execution happens in separate Docker containers.
In case of REPL, you send STDIN to websocket and get STDOUT as response. All code execution happens in separate Docker containers.
Email me at hn at vikas.sh if you have a service. I'd need an SLA for sure, and multi-file support would be nice to have.
We've been running it for over a year and would be willing to talk about an SLA. Each instance gets its own gvisor-sandboxed runtime and we do some network isolation on top of that. (We also have some crypto miner mitigation, because if you provide free compute to strangers they will manage to find you.)
I am sure there are many whom would. Some may use it ethically, but many will not.
All will place liability on the service.
I wonder if repl.it ever did this, or if they've always used WebAssembly? (They definitely use wasm now.)
I believe the very first version of replit was all in-browser, but no longer
Wow, that's a change. I remember using replit with Python compiled to wasm. It was neat for a few seconds.