News for hackers. Stuff that matters.
Re:MRSK vs. Fly.io by theonething on Thursday March 23, 2023 @02:45AM (#35271214)
> I'll never understand these arguments against Kubernetes and its complexity

Because my project doesn't need the benefits that K8s offers. Why choose the more complex solution when I don't need it? And judging from experience and what others have shared, most projects will not need it.

> no way to debug it or move off it

If a managed service is down, the host company debugs it. That's the whole point of a managed service, so I don't have to do devops.

Why would there be no way to move off of it? PaaS is so easy to onboard and deploy, you can move to other services easily.

> It feels like many developers these days are so spoiled by magic services that they are unwilling to even spend a few days going deep into something

Why don't you go all the way and build your own physical servers instead of using these magic cloud machines? That way you can go deep into it, and if they have problems, you can debug yourself.

If you enjoy building and maintaining your own K8s clusters and you feel it benefits you, great for you. But don't be so condescending to people who don't feel the same and choose the simple infra solution because they'd rather go deep into building their application rather than spending time with K8s. Calling them spoiled for that is just obnoxious.

Re:MRSK vs. Fly.io by YetAnotherNick on Thursday March 23, 2023 @04:48AM (#35271940)
> Because my project doesn't need the benefits that K8s offers.

So what? It just takes a month long time investment to be used to kubernetes(many people already have some experience from working for employers), and after that it takes one or two days extra days to make some project as easy to deploy as heroku. So basically it is a fixed learning cost. Obviously if someone is looking to get something up as soon as possible and doesn't have kubernetes experience, it is better to not use it.

But for me, the fixed learning cost clearly paid off. Kubernetes is lot better than alternatives if you want to assign fine grained securities, namespaces, complex scaling rules, using multiple clouds, multiple node types etc. Even if I don't need any of these now, I am not giving any extra time investment for new projects and it guarantees I don't need to do any migration to some other form of deployment if my project becomes big.

Re:MRSK vs. Fly.io by bryanrasmussen on Thursday March 23, 2023 @06:11AM (#35272430)
> It just takes a month long time investment to be used to kubernetes

Ok so next time I'm laid off I will have some tech to choose learning. May I will spend that month.

Even when I wasn't a parent I don't think my life was that open that I could say well it only takes a month, I guess I will learn that. Lots of things take a month to learn. people pick and choose.

Re:MRSK vs. Fly.io by rat9988 on Thursday March 23, 2023 @07:21AM (#35272993)
I'm pretty sure he meant a month of your job.
Re:MRSK vs. Fly.io by replygirl on Thursday March 23, 2023 @08:56AM (#35273991)
gp prolly has stuff to do at the job.
Re:MRSK vs. Fly.io by bryanrasmussen on Thursday March 23, 2023 @09:45AM (#35274701)
exactly. but if it is a month of my job that means my employer needs to choose that I start learning it.
Re:MRSK vs. Fly.io by rat9988 on Thursday March 23, 2023 @12:16PM (#35277081)
That's exactly what we all meant.