That seems like another strawman; e.g. I said it could be warrants for this reason.
There's lots of examples of financial ownership without the holder of the return running the business. Whether it's a state or an ex-spouse.
46 karma · joined January 7, 2010
There's lots of examples of financial ownership without the holder of the return running the business. Whether it's a state or an ex-spouse.
Maybe you could pay it in shares, so no borrowing required.
Or maybe for illiquid assets including non-public stock it could be warrants that you only have to settle at a liquidity event.
It's a strawman to assume a wealth tax will be set up in a broken way when non-broken ways are possible.
I think these should be able to add up to more than 100. E.g., someone who is both Hispanic and Black.
Tilt is just for precommit development.
If you email me (dan @ windmill dot engineering), we can talk more, but we are more reproducible and less config than mounting directories into minikube.
If you use skaffold for local dev, a Tiltfile will take 10 minutes to write. Email me at dan at windmill dot engineering and we can pair to get you going. You're the user who would benefit from Tilt immediately.
Tilt replaces `docker build && kubectl apply` or `docker-compose`. It watches your files, updates automatically, and gives you a UI that shows you error so you don't have to spelunk with kubectl.
It uses minikube or docker-for-desktop or a cloud k8s cluster (AKS, EKS, GKE, whatever).
It's like skaffold or draft or garden.
Does that help?
We think you deserve three properties: 1) it's easy to start your whole app 2) it's fast to update your app as you edit 3) common problems can't be missed.
docker-compose gives you 1. (some people hack in mount points and file watching to get 2, but it's hacky)
skaffold and garden.io give you 1 and some of 2. (Tilt has fast_build, which can update pods in-place, without rebuilding the whole image, which I don't believe either skaffold or garden.io do)
Our big value-add is the UI. Which may sound weird for a Terminal UI, but if you look at the demo video on https://tilt.build , I think you'll get a sense for how Tilt is working to keep the problem that's blocking you in your face, so you don't waste time playing 20 questions with kubectl.
You can just call k8s_yaml(local('helm template <args>')). That tells Tilt to parse the yaml generated by running (locally) helm template. Feel free to reach out if you'd like to pair to try it.
The problem this solves is that distsys devs don't get enough feedback. You say you use docker-compose. Compared to docker-compose, Tilt has two advantages: 1) It updates the services as you edit them 2) Its UI makes it easy to see where errors are occurring, without you having to play 20 questions on the command-line or worry about things scrolling off-screen.
The Tiltfile doesn't redefine your k8s definitions; it reuses your existing k8s definitions. The Tiltfile just tells Tilt how to get them. (Many teams don't just use yaml files, but generate them, so Tilt has to be able to do that, too.)
There is a landing page at https://tilt.build which has more of the "why Tilt". Also, we're adding native support for docker-compose next week. I'd love to understand your case more, because at a high level you sound like exactly the kind of dev we want to help.