And I hope we can keep it that way, in spite of increasing polarisation everywhere. The world is not a good place if people can't see eye to eye and have some basic level of understanding.
You're right, but between my carrier and Meta, I'd prefer to trust my carrier, even if it's just to know which window to throw a brick through. Maybe I'm being too European on this, but I'm not willing to hand over basic communications to private industry, especially companies whose entire business strategy is building profiles on people.
I still hope for a protocol to win out that's not tied to one party.
Between your carrier and Meta, the choice is clear, but your carrier is almost certainly not a saint. Between your carrier and literally and open source message service, Signal being the obvious one, the choice is again clear.
Not to mention that the choice isn't really between your carrier and Meta, but rather Google and Meta, since most people on Android end up just using Google servers for RCS, and that choice is much more of a toss-up.
I feel the same, especially the feeling old and jaded part, but I disagree that things were easier. Systems such as Kubernetes are not worse than trying to administer a zillion servers and networks by hand in the late '90s (or with tools like Puppet and Ansible a bit later), let alone HA shenanigans; neither are they a magical solution, more of a side-step and necessary evolution of scale.
There is a wild-grow of 80% solved problems in the Kubernetes space though, and especially the DevOps landscape seems to be plagued by half-solutions at the moment.
I think part of the complexity arises from everything being interconnected services instead of simple stand-alone software binaries. Things talking with other things, not necessarily from the same maker or ecosystem.
I don't understand decisions such as these though, retiring de facto standards such as Ingress NGINX. I can't name a single of our customers at $WORKPLACE that's running something else.
If you count 3 control plane nodes and at least one or two extra servers worth of space for pods to go when a node goes down, I'd say don't bother for anything less than 6-7 servers worth of infrastructure. Once you're over 10 servers, you can start using node affinity and labels to have some logical grouping based on hardware type and/or tenants. At that point it's just one big computer and the abstraction starts to really pay off compared to manually dealing with servers and installation scripts.
I'd say the abstraction is not worth it when you have only a steady 2-3 servers worth of infrastructure. Don't do it at "Hello, world!" scale, you win nothing.
(I work for a company that helps other companies set up and secure larger projects into environments like Kubernetes.)
Latitude is one factor but not the sole factor, proximity to oceans/seas for example matters as well as it has a moderating influence in both dimensions - not a coincidence that the coldest states in the continental US are all northern and in the center of the landmass.
Other factors are things like prevailing winds, mountain ranges, altitude and so on and on - the climate system is one of the most complex systems on the planet and even with decades of heavy study and insanely fast computers we still struggle to predict it accurately out past a week or two at most with any degree of success.
I think there is some value in being able to live in the moment, like say a cat: one moment you have a death scare, the next you're kind of hungry or sleepy. I feel that smart people see a lot more in the past, present and future, all the things themselves, and the things behind the things, and it's a whole lot harder to live in the moment and not ruminate and dwell on things.
Alternatively, maybe it's just that overthinking that is driving some aspect of what we call intelligence; the ability to plan and see things in complex layers.
Good amounts of happiness surely require some selective blindness.
Lots of medical and governmental organisations are not allowed to run in public cloud environments. It's part of my job to help them get set up. However, in reality that often boils down to devs wining about adding a registry to Harbor to cache; nobody is going to recompile base images and read through millions of lines of third party code.
A lot of security is posturing and posing to legally cover your ass by following an almost arbitrary set of regulations. In practice, most end up running the same code as the rest of us anyway. People need to get stuff done.
reply