Hacker News new | ask | show | jobs
by gotaran 726 days ago
Modern day Kubernetes and React feels like a make work program
2 comments

The thing about Kubernetes is: Its a cloud in a box. It re-implements a ton of the functionality that cloud platforms already offered. But, no one wants to host their own kubernetes, so you go to AWS/GCP/Azure, and you just end up duplicating everything.

But I think the industry is waking up to this; there's just a lot of sunk cost. Kubernetes makes a ton of sense, for some organizations, but if you're not hosting your own machines in a data center somewhere, its probably not for your organization and you'll always be better off just using the highest abstraction level non-k8s primitives your cloud provider offers.

React: Is in a different league. React solves legit problems. UI is hard. React doesn't create zero problems of its own, and some of those problems are of the "we thought redux was the best way to think about this, we were wrong, but now there's a billion lines of redux out there" variety, which sucks because it was self-inflicted. Also, you've got the Vercel folks entirely convinced they're God's Gift to Humanity steering the ship in directions no one really wants. But the core of React is really good: fn(state)->ui.

React at its core is great. Redux is great too, as vanilla React becomes messy even for moderately complex single page apps.

Whatever it’s evolved into now is a different monster.

It’s amazing that we’ve flipped from “put the workload on the server to make it faster” to “run the workload on your midrange laptop over WiFi so it finishes in a quarter the time the server would take”.

That’s entirely due to “the cloud” and k8s and friends.

You're doing cloud and k8s very wrong if your midrange laptop can beat it. Don't blame tools for your lack of knowledge. It's a complex tool for complex situations, it's not its job to make everything super easy for you. Just don't use it or let someone who knows how handle it.