Oh this would be such a good fit for my dream of serving federated backend code from web readable hosting https://webcode.run/. - Source: Hacker News / over 1 year ago

This would be so amazing. In order to access most vanilla services like redis, postgres etc. You need to deploy a bridge https://github.com/zquestz/ws-tcp-proxy -- somewhat abandoned at this point but it is still running), and a big problem with the approach was the web's inability to make TCP connections. - Source: Hacker News / about 2 years ago

Yeah, you are right. I made https://webcode.run also for this reason (also hot code reload and debugging but for JavaScript computational notebooks). - Source: Hacker News / over 2 years ago

This was why I created https://webcode.run the elimination of all tooling and a fast development loop even for backend. - Source: Hacker News / almost 3 years ago

I am building a compute layer for Observablehq which enables services to brought up using nothing other than a web browser. It's a bit too soon to call it a K8s replacement but the motivation was the complexity and laggyness of bringing up services on cloud or k8s. The WEB + on demand infrastructure is the distributed replacement of K8S https://webcode.run/ WEBCode is about eliminating environments and the... - Source: Hacker News / over 3 years ago

Working on Runno (https://runno.dev/) as a side project. It's a tool for running code in the browser for educational use. I've been playing around with turning it into a sandbox for running code in Python (https://runno.dev/articles/sandbox-python/). This would allow you to safely execute AI generated code. Generally thinking about more ways to run code in sandbox environments, as I think this will become more... - Source: Hacker News / about 1 month ago

Really impressed by the depth and breadth of this project, well done! A particularly interesting part is the socket layer inside the browser. Other people solving this problem have previously used a proxy to a server that does the real socket implementation. This means you can't have a "browser-only" solution. The author has solved this (for HTTP/S only) by proxying HTTP requests and then re-creating them as fetch... - Source: Hacker News / over 1 year ago

This is the use case I've been tackling with Runno (https://runno.dev), it's more performant than OP's approach but not as flexible. - Source: Hacker News / over 1 year ago

I love these kinds of interactive code/sandbox projects! The author's example page [1] gives some more background on the design of Codapi as well [2]. Another similar project is Runno which runs entirely client-side in the browser [3]. [1] https://antonz.org/code-examples/ [2] https://codapi.org/ [3] https://runno.dev/. - Source: Hacker News / over 1 year ago

I'm working on this problem as well and would be happy to sling you some thoughts and notes. Check my website https://runno.dev and send an email to the address on that website! - Source: Hacker News / over 1 year ago