kryptn

I definitely prefer using kustomize over helm, where the mentioned interpolation takes place.

While reading Pushing Ice a very common thought I had was "did Reynolds want to do a Rama sequels?"

Shroud is great, easy recommendation. Another of Tchaikovsky, Alien Clay, also great, also very alien.

I enjoyed the sequels but they're a completely separate story to me, and I don't think I'd read them again.

I didn't go in with the expectation that they'd be just like Rendezvous with Rama.

Nope, just used their web chat support.

this happened to someone i was helping. we went to support. they now have an apple id.

was interesting, some of our stuff failed, but some other stuff that used cloudflare indirectly didn't.

i decided to use htmx for a frontend for myself and it was a pretty fun experience. even got tailwind involved pretty easily with my rust+maud backend.

htmx isn't local first. this blog post is about trying to make it 'local first' by introducing a service worker.

Mind elaborating?

we throw things through yq for formatting

> To a k8s engineer, serverless means “no servers”!

I'd assume a majority of people working with k8s knows what serverless is and where Functions as a Service work more generically.

The rest of the post just seems to be full of strawman arguments.

who is this kubernetes engineer villain? It sounds like a bad coworker at a company with a toxic culture, or a serverless advocate complaining at a bar after a bad meeting.

> k8s is great for container orchestration and complex workloads, while serverless shines for event-driven, auto-scaling applications.

> But will a k8s engineer ever admit that?

Of course. I manage k8s clusters in aws with eks. We use karpenter for autoscaling. A lot of our system is argo workflows, but we've also got a dozen or so services running.

We also have some large step functions written by a team that chose use lambda because aws can handle that kind of scaling much better than we would have wanted to in k8s.