lann

Yes.

Clearly they are referring to the years 1029 and 1032 (decimal). I just want to know what calendar system they're using...

This comment really assumes you know the acronym LLM

One specific example: many languages use randomized seeds in builtin dict/map types, leading to randomized iteration order.

Sarcastic replies can be fine. Sarcastic replies when you clearly didn't read the article are just annoying.

Nationally yes, but states can do it independently (piecemeal).

Top-2 is a primary system, not a voting system. When combined with (essentially a generalized version of) FPTP you get most of the same problems.

Or actually radical: switch from our terrible first-past-the-post voting system to - say - ranked choice (or one of many alternatives; they're almost all better than fptp) and then primaries won't be so important and parties won't have so much power over our kinda-democratic-but-actually-oligarchic political system.

The answer depends on the specific CRDT algorithm in use. For complex data structures like the ones behind collaborative text editing your intuition that the updates end up looking hierarchical is generally correct.

It is probably an error message on a very unlikely failure path / assertion. Those sorts of messages are effectively just comments.

I looked at a bunch a while back and found this to be a nice middle ground with a usable mobile interface: https://floorplancreator.net/

Paid version can export to DXF (AutoCAD)

Yes, on most[1] hardware: https://chromeos.dev/en/linux

[1] Released since 2019 plus these: https://sites.google.com/a/chromium.org/dev/chromium-os/chro...

To this specific point, SCIFs (https://en.m.wikipedia.org/wiki/Sensitive_compartmented_info...) are (allegedly) protected by faraday cages.

A bit of a tangent, but board members (and company officers) do not in general have a specific duty to maximize shareholder profit. They have a duty of care (think carefully about decisions) and a duty of loyalty (act in the best interests of the company as a whole). Those could lead reasonably to a profit-maximizing decision but it isn't a straight line.

> Psuedo-RNGs typically use an algorithm (such as a hash) which is very hard to reverse.

Note that this is only necessarily a property of Cryptographically Secure PRNGs. Some PRNGs are not designed to be difficult to predict at all.

I don't know much about Lagrange points specifically, but it sounds like this one is an "unstable equilibrium". Even if you could park on exactly the right point, any tiny force (changing gravitational pull of other planets, dust impact, even light pressure from the sun eventually) would nudge you off of it and you would start accelerating away from it.

There is a `git mv` command that means "rename". Git could (even with its current data model) explicitly annotate commits with this intent, but doesn't. I don't know how useful that would be compared to the current heuristics, but it does mean that git commit "snapshots" are not (quite) isomorphic to a diff format (like posix diff's) that can explicitly encode renames.

> aren’t commits isomorphic to diffs?

Nearly, though renames are only approximately extracted from the snapshots.

You could trigger on any keypress on a first-time site.

Fiduciary duty does not mean "must make money at the expense of all other considerations".

> Brigade has a duty to its investors to fight tooth and nail to keep this money

What kind of duty? Not a legal one, I think.

It's worth noting that you are the author of RON :)

Check out zerotier; I've been looking at similar p2p techniques and ZT does a good job of packaging them all up with a relaying fallback.

Sounds familiar, but Xcode does actually provide a bunch of CLI tools...

> something consumable

ESP8266s can be had for ~$1...

You are misunderstanding what you are seeing. The Z does not represent a literal Z in parsing/formatting.

https://play.golang.org/p/Qp-bBtzKpG-

Go has an unusual way of specifying date formats. The "example" timestamp is a format spec and I believe the 'Z' will correctly handle offset signs.

From the docs:

Replacing the sign in the format with a Z triggers the ISO 8601 behavior of printing Z instead of an offset for the UTC zone.

If the sleep is some kind of busy wait then I think it is something like O(m*n) where m=max number.

If it is scheduled by the kernel then the complexity is hidden in the scheduling algorithm.