Also, maybe dont rely on a poorly maintained app for making secure connections to your systems? Just me?
Also, maybe dont rely on a poorly maintained app for making secure connections to your systems? Just me?
This tagline at the end of the website is one of those formulas that I can't help but link to language models.
I'm not saying it couldn't come from a human but since I started noticing it, I find it so cheesy and patronizing, it gets on my nerves.
Example: https://www.microchip.com/en-us/products/clock-and-timing/co...
It's a huge huge huge misconception that you can just plunk down an "atomic clock", discipline an NTP server with it and get perfect wallclock time out of it forever. That is just not how it works. Two hydrogen masers sitting next to each other will drift. Two globally distributed networks of hydrogen masers will drift. They cannot NOT drift. The universe just be that way.
UTC is by definition a consensus; there is no clock in the entire world that one could say is exactly tracking it.
Google probably has the gear and the global distribution that they could probably keep pretty close over 30-60 days, but they are assuredly not trying to keep their own independent time standard. Their goal is to keep events correlated on their own network, and for that they just need good internal distribution and consensus, and they are at the point where doing that internally makes sense. But this is the same problem on any size network.
Honestly for just NTP, I've never really seen evidence that anything better than a good GPS disciplined TCXO even matters. The reason they offer these oscillators in such devices is because they usually do additional duties like running PtP or distributing a local 10mhz reference where their specific performance characteristics are more useful. Rubidium, for instance, is very stable at short timescales but has awful long term stability.
I would have probably approached this by implementing a fix for the misbehaving part of k8s, though since there isnt a default LoadBalancer in k8s, I can't really can't speculate further as to the root cause of the initial problem. But most CNI or cloud providers that implement LB do have a way to take feedback from an external metric. I'd be curious why doing it this way wasn't considered, at least.
The JavaScript instruction is cooler though.
https://developer.arm.com/documentation/dui0801/g/A64-Floati...
Changing the HN headline to soften the project's own bombastic claim isn't really the point of the argument. It would bhe better to highlight any project that is actually working on open source microscopy of which there are many. Flagged
I don't know if it's because of context clogging or that the model can't tell what's a high quality source from garbage.
I've defaulted to web search off and turn it on via the tools menu as needed.
My theory was that the carbonation was perfect and the product was fresher, as the bottler requires rabbinical supervision and they probably make it for a limited run.