zlacker

We could but decided against it because we have no way to run those efficiently given our architecture and prefer to support a few languages and ensure we can run them blazing fast than all languages but with no guarantees of performance. In windmill, you have the guarantee to have no cold-start thanks to leveraging the great design of the deno runtime. For python, we had to do a LOT of engineering to make it work well and did not have the bandwidth to do the same for all languages. Ultimately, we could decide that some steps could be slow and it doesn't matter but it wasn't requested enough to prioritize it.

To be clear, the workers can run in docker, but do not run docker jobs.

>>rubenf+(OP)
Thanks for the clarification.

Looks like you're a new y combinator startup. Kool. I would suggest you find away to allow existing code to be reused. Deno market share is very small and experienced/larger teams are not going to want to rewrite and learn that stack. They would have to depend on you, a small new company. Too much risk.

>>ttt3ts+J2
It depends on how efficient you need to be. There is the option to just use "shell" scripts where you run the command. I haven't done much with that, but it's there.