In a professional setting, sometimes the cost of developing something more performant in C is not worth it. The velocity unlocked by creating systems in Go is just incredible, after your company has built everything in C[++] for decades. I find myself creating gRPC APIs in Go to solve most design challenges, because it's stupid fast to develop and is fairly maintainable after.
Has citizenship in two countries, but identifies as sovereign...
If these people actually want to be sovereign, the only way I can imagine that working is living on a boat at sea, far away from land, for the rest of their lives.
Some of these sovcits are trying to solve an imaginary puzzle, this guy is something else.
Seriously though, these appear to be the thoughts of a mentally unwell person - if you actually have contact with this person OP - make sure someone is in charge of his meds.
Not cross country but northeast corridor is fantastic - DC to Boston, ezpz. Faster than flight with the BS you need to do on both sides. Also the stations are in the hearts of the city of DC, Philly, NYC, and Boston - get off the train and walk to your hotel or whatever - it's just the best.
K8s has a mild solution to chicken and egg situations for nodes - the nodes support 'static manifests' which can be pods they know how to bring up before ever connecting to the API server. So you could have your wireguard peer be brought up this way. Downside is while those static manifests show up in k8s APIs, they aren't fully manageable since they are defined by files on disk.
Wave soldering machine - they basically suspend the whole board above a vat of solder, it bonds anywhere it can. So if they don't need that chip on this model, it's getting solder anyway.
Sometimes I wonder if in 75 years people will look back on our caffeine use in this generation like we currently look back at cocaine use in products in the 19th century. Until then, I continue to slurp down coffee like that is my actual job.
Chilli dogs, actually