Show HN: I made an in-browser code editor with code replay and REPL
11–20 of 29 posts
Re: Show HN: I made an in-browser code editor with code replay and REPL
#12Earlier quoted context omitted.
Docker containers probably aren’t enough isolation. But throw some firecrackervm in the pot and you’ve got a stew going.
Repl.it uses Docker containers too, only recently started work on moving to better isolation mechanisms like VMs
Re: Show HN: I made an in-browser code editor with code replay and REPL
#13I'm curious if anyone would like to use the code-execution as a service. It's basically a websocket based API where you send a blob of code and get execution result as response. 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. 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
Re: Show HN: I made an in-browser code editor with code replay and REPL
#14Where is the code being executed?
Re: Show HN: I made an in-browser code editor with code replay and REPL
#15Re: Show HN: I made an in-browser code editor with code replay and REPL
#16Is that code mirror?
Re: Show HN: I made an in-browser code editor with code replay and REPL
#17Nice use of phoenix liveview (I'm assuming). The app is really smooth, and executes rust faster than the official rust playground
Re: Show HN: I made an in-browser code editor with code replay and REPL
#18Where is the code being executed?
Re: Show HN: I made an in-browser code editor with code replay and REPL
#19I just ran a couple of Python scripts that grabbed the ec2 instance metadata and the HN front page.
Re: Show HN: I made an in-browser code editor with code replay and REPL
#20I'm curious if anyone would like to use the code-execution as a service. It's basically a websocket based API where you send a blob of code and get execution result as response. In case of REPL, you send STDIN to websocket and get STDOUT as response. All code execution happens in separate Docker containers.
I am sure there are many whom would. Some may use it ethically, but many will not.
All will place liability on the service.