AFAIK continuously welded tracks (like those used in high speed rail) are also slightly tensioned, so a break in a single point could make it look like a whole section of track is missing, as tension is released.
Genuinely interested. What problems did you have dealing with the standard reconciliation mechanism provided by ArgoCD and by k8s itself. I understand the advantage of the operator approach, but it might be hard to show the state in ArgoCD and somewhat breaks the idea of gitops.
Can we benefit your project in a more limited but agentless way? Limiting the types and CRDs we allow in k8s makes operations better, especially with the aggressive upgrade cycle that k8s already imposes.
This is a problem for me as a language learner on mobile. I set a keyboard with (for example) Russian, and suddenly the world looks Russian, even though I am far from comfortable in it yet. I wish there were a way for the browser to ignore some system languages. This is worse for apps because I also get served with localised versions, where I need to uninstall, remove system language and re-install.
Deep down in the sun photons are absorbed almost as soon as they are created. In a sense the photons at the surface of the sun are the result of nuclear reactions thousands of years back. However neutrinos escape pretty fast and so can be used to gauge the status of nuclear reactions now.
In some restricted environments (e.g. containers in CI, build servers or AWS Lambda) you may have limited disk space or no write access at all, so it is useful to have a tool that can stream to memory while decompressing on the fly, and discarding what you don't need.
The ancient Roman concrete was very different from modern: it was more thick, could not ne poured etc. But more importantly, it had no rebar, which is the main thing that corrodes over time. Ancient buildings could use molten lead to join together pieces of stone, but steel could not be made in the volume needed for reinforced structures.
> The goal is to define a datatype by cases, where one can add new cases to the datatype and new functions over the datatype, without recompiling existing code, and while retaining static type safety (e.g., no casts).
Isn't this made moot by the prevalence of static linking or fat binaries in go-land?