Live data from Hacker News

Tilt – Local Kubernetes development with no stress

github.com

71–76 of 76 posts

Re: Tilt – Local Kubernetes development with no stress

#71
post #60
post #31

Earlier quoted context omitted.

Hey, I'm CEO of Tilt. Thanks for the feedback. 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 Tiltf…

> (Many teams don't just use yaml files, but generate them, so Tilt has to be able to do that, too.) Tell me more about this? I have my own helm like product and I had issues getting that to work with skaffold.

Helm is one way to generate k8s yaml. There's also kustomize, or ksonnet, or custom scripts (sed!).

Re: Tilt – Local Kubernetes development with no stress

#72
post #55

Earlier quoted context omitted.

I don't see how Starlark is better... Does it validate what you write somehow - in a way that couldn't be done by validating a YAML?

I don't understand, I'm not talking about Starlark..?

Meant to reply to the comment, sorry :)

Re: Tilt – Local Kubernetes development with no stress

#73
post #31

Earlier quoted context omitted.

Hey, I'm CEO of Tilt. Thanks for the feedback. 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 Tiltf…

It looks like your basically recompiling/rebuilding the container and just updating what’s running (in what I assume is a k8s cluster on OS X). This all seems like a terrible idea. No way devs want to wait for a container rebuild to see updated code changes, that’s highly unproductive. They usually don’t run k8s locally either, because it’s an abstraction later they hardly want/need to concern themselves with while w…

That's why we have fast_build, which does something more clever. I just published a Blog Post "How Tilt Updates Kubernetes in Seconds, not Minutes": https://medium.com/windmill-engineering/how-tilt-updates-kub...

Re: Tilt – Local Kubernetes development with no stress

#74
post #31

Earlier quoted context omitted.

Hey, I'm CEO of Tilt. Thanks for the feedback. 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 Tiltf…

> There is a landing page at https://tilt.build which has more of the "why Tilt". As a tangential by-the-way, I notice you're based in NYC. Of interest, Googlers working on Knative Build (hi Jason!) and Pivots working on Cloud Native Buildpacks (including me) are based in NYC also.

As puzzle mentioned, yep. I know Jason pretty well. Happy to chat; want to get coffee? I'm dan at windmill dot engineering for scheduling.

Re: Tilt – Local Kubernetes development with no stress

#75

Earlier quoted context omitted.

Docker containers/lxc require Linux. They are a Linux technology.

As weird as it sounds, Microsoft had implemented the full namespaces stack in Server 2016 (unavailable in Win10 as the base for native containers is Server where kernel differs a bit), which Docker supports (and k8s in alpha/early beta). Docker switched from LXC to containerd in 2016.

That is very weird. Wow. Thanks for letting me know. I guess it's not a Linux technology then.
Post reply on HN