Show HN: A Lisp where each function call runs a Docker container

\u003ch2\u003eShow HN: A Lisp where each function call runs a Docker container\u003c/h2\u003e \u003cp\u003eThis Hacker News "Show HN" post presents an innovative project or tool created by developers for the community. The submission represents technical innovation and problem-solving in action.\u003c/p\u003e \u003ch3\u003eProject Highlights\u003c/h3\u003e \u003cp\u003eKey aspects that make this project noteworthy:\u003c/p\u003e \u003cul\u003e \u003cli\u003eOpen-source approach promoting collaboration\u003c/li\u003e \u003cli\u003ePractical solution to real-world problems\u003c/li\u003e \u003cli\u003eTechnical innovation in software development\u003c/li\u003e \u003cli\u003eCommunity engagement and feedback-driven improvement\u003c/li\u003e \u003c/ul\u003e \u003ch3\u003eTechnical Significance\u003c/h3\u003e \u003cp\u003eThis type of project demonstrates the power of community-driven development and the continuous evolution of technical solutions through collaborative efforts.\u003c/p\u003e

Frequently Asked Questions

What is a Lisp where each function call runs a Docker container?

This project is an experimental Lisp dialect that treats Docker containers as first-class execution units. Instead of calling a function that runs inline, each function invocation spins up an isolated Docker container to perform the computation. This approach provides strong sandboxing, reproducibility, and the ability to use different language runtimes or environments per function — all within a unified Lisp syntax and evaluation model.

What are the practical use cases for this kind of containerized Lisp?

The most compelling use cases include running untrusted code safely, orchestrating multi-language pipelines, and building highly isolated microservice-style workflows from a single scripting environment. Developers building automation platforms — similar to what Mewayz offers across its 207 modules at $19/mo — can use this model to safely execute user-defined logic without risking host system contamination or dependency conflicts.

What are the performance trade-offs of running a Docker container per function call?

The main trade-off is latency. Container startup times typically range from hundreds of milliseconds to several seconds, making this approach unsuitable for hot code paths or tight loops. It is best suited for coarse-grained, side-effectful, or long-running tasks where isolation justifies the overhead. Caching pre-warmed containers or using lightweight runtimes like gVisor can help reduce startup penalties significantly.

Is this project production-ready or more of a research prototype?

Based on the "Show HN" framing, this is best treated as an early-stage research prototype exploring an unconventional execution model. It demonstrates strong conceptual value but would require significant hardening — error handling, resource limits, orchestration — before production use. If you need production-grade workflow tooling today, platforms like Mewayz provide 207 ready-to-use modules at $19/mo as a more stable alternative.