96 karma · joined August 13, 2024
It’s a choice the maintainer has to make.
To me this is mostly self inflicted pain…
The reality is different - they leave these huge red flags so that people who aren’t very bright or careful will fall for it.
That is the same reason why scammers put spelling mistakes in emails - not because they don’t know how to use spellcheck, but because they want to filter out those who would spot these mistakes.
They want to scam careless, gullible, „stupid“ people, not someone who is careful enough to spot security red flags.
> The United States leads the world in total number of people incarcerated, with more than 2 million prisoners nationwide
https://en.m.wikipedia.org/wiki/Incarceration_in_the_United_...
Sorry but that’s a fantasy. I live in Germany and that is 100% not the case here. You might be able to negotiate it if you are an especially valuable employee but normally no chance
- Your current cloud / PaaS costs are north of $5,000/month - You have at least two developers who are into the idea of running Kubernetes and their own infrastructure and are willing to spend some time learning how to do so
So you will spend 150k+/year (2 senior full stake eng salaries in EU - can be much higher, esp for people up to the task) to save 60k+/y in infra costs?
Does not compute for me - is the lock-in that bad?
I understand it for very small/simple use cases - but then do you need k8s at all?
It feels like the ones who will benefit the most is orgs who spend much more on cloud costs - but they need SLAs, compliance and a dozen other enterprisy things.
So I struggle to understand who would benefit from this stack reclaim.
That sounds insane, is that actually happening in practice? What is the point?
I guess the method described here does „more“ since it’s much more elaborate. Not super familiar with the different levels of win licences