Yes it's a CLI REPL, you build and run the binary using the instructions in the README and then create/insert/select from it by typing those commands into the CLI.
Currently there's no way to connect to it like you would a normal SQL db, but you could embed it like you would sqlite.
Lots and lots of home users care more about the few % of performance than the nebulous "extra security".
I have friends who use their desktop for gaming only, literally nothing else, I guarantee they don't care about the extra security a microkernel claims to offer.
Obviously the concern is an escalation of that war which pulls NATO into the conflict fully. I don't believe that's a likely scenario, but being deliberately obtuse isn't the right way address that somebody expressing that concern.
The argument that was made (and that was not central to the post at all, despite everyone jumping on it) is the slow erosion of freedoms that may lead to less restraint also in foreign affairs.
UK politicians have been periodically demanding NATO engagement, though this one is from 2022:
When synchronizing two nodes A and B, where there is a persistent difference in the travel times A->B and B->A, how do you achieve synchronization when knowing A->B->A or B->A->B?
Delay symmetry is a critical assumption in any two-way time transfer process. White Rabbit goes to extreme lengths to maintain that property.
This includes mandating use of cables that share a single optical fiber, with specific wavelength pairs and fiber types so you can calibrate for unavoidable differences in propagation time.
you can't. You can only assume that they are equal and attempt to make them as equal as possible. (the same issue arises when measuring the speed of light: it's actually not possible to distinguish if the speed of light is different in one direction to another, we only know accurately the average of each direction)
The roundtrip time is never consistent. Light travels with different speed in fiber depending on the temperature. This is why you calibrate every second.
Even better, the actual in situ delays are measured and compensated for, and it works independent of the physical connection (and through fiber/copper, switch layers, etc.).
Indeed. It's exactly the same (albeit on a different scale) as NTP synchronization, where you can frequently (ha!) reach a few ms accuracy over a hundred ms latency network.
Github Enterprise hasn't been faring too well at my work either this week. When you work on both open and closed source products and GH and GHE are both down, it leads to a very unproductive week.
GitHub Enterprise is confusingly both a "call us for pricing" tier of GitHub the website, and also an on-premise version of GitHub that you can run as an appliance in your own data centre. The first of those is ultimately just GitHub and so has the same outages, the second is running on your own hardware so (shouldn't be) tied to the website's availability.
There are multiple products: self-hosted (Enterprise Server) and hosted by GitHub (Enterprise Cloud). I don't know about uptime guarantees, but you can buy Premium or Premium Plus support with 30-minute SLA or a dedicated account manager.
Currently there's no way to connect to it like you would a normal SQL db, but you could embed it like you would sqlite.