kurtosis

We used Starlark for all of its properties and built a tool[0] that allows you to spin up containers in an imperative programming way on Docker and Kubernetes through Starlark! It can be pretty cool as you can pass in arguments and get a different set of services based on what you pass in. I like to think of it is an "exe" for a distributed system. [0]https://github.com/kurtosis-tech/kurtosis

100%. Containers are essentially language-agnostic software libraries, and the config we write for them is analogous to the wiring we'd normally do in a to wire libraries together. Yet, our current tools aren't adapted to write and distribute the "programs" formed from gluing them together. (Mostly-shameless plug, this is what we're trying to solve with Kurtosis: https://github.com/kurtosis-tech/kurtosis )

Obviously biased but we at Kurtosis are trying to solve this problem through Starlark. We took Starlark added a few more of our instructions that make our Starlark container native. The complex Starlark definition supports - Composition - you can import a remote definition and just use it - Decomposable - you can break things apart - Parametrizability - want one of a service and 10 of the other, just pass an argument - Portable - It runs pretty much anywhere Our runtime takes the Starlark and creates environments in both Docker and Kubernetes; from one definition Our CTO wrote this - https://docs.kurtosis.com/advanced-concepts/why-kurtosis-sta... We are source available https://github.com/kurtosis-tech/kurtosis Here is a popular environment definition - https://github.com/kurtosis-tech/ethereum-package that protocol developers use to setu

I chuckled reading this, as we're trying to do exactly what you described at my current startup, https://github.com/kurtosis-tech/kurtosis ! More seriously, I've been mulling over the idea that humanity is going through a continual process of modularization and unification: First came machines, to perform simple "computation" tasks. Then came the computer with instructions to represent the generalized notion of computational work. Then we wanted a way to DRY instructions so we got functions. Then we wanted a way to package collections of functions so we got libraries. Then we wanted a way to manage collections of libraries so we got package managers. Then we wanted a way to distribute collections of packages so we got containers. Now we're in a world where instantiating and configuring a collection of containers is error-prone, burdensome

We're trying to do this at Kurtosis! (https://github.com/kurtosis-tech/kurtosis) The idea is to write your environment in Starlark (a minimal Python subset) and we'll handle running it on Docker or Kubernetes for you. We started with "reduce Kubernetes complexity" so we don't yet have the full Kubernetes ejection seat, but we're slowly marching towards it - feedback welcome!

Hey djupblue, right here! https://github.com/kurtosis-tech/kurtosis/#:~:text=Check%20o...

I'm building a Starlark-based build system that operates at the level of building multi-container environments, rather than normal code assets: https://github.com/kurtosis-tech/kurtosis It's kind of like Docker in the sense that it packages up an application in a reproducible, composable, and portable way...but instead of working at the level of one server, it works at the level of multi-server applications. In the back of my head I'm very curious about making an application that just messages me on WhatsApp whenever its the birthday of one of my close friends because I never remember those