once my codex/claude weekly limit was gone, i gave it a try. It was surprisingly good, not dumb in any way, and fast. I now require it as a part of 3-of-3 quorum with any codebase change.
macOS Codex app is my main agent (its very polished). When it makes changes or code scans i ask it to run claude -p plus cursor-cli plus grok cli for double checking. This way bias of one model can be overruled by quorum.
You can't do any real money/real estate transactions without canonical order (chain of events). that's why git analogy is not applicable here. You'd need "main" branch to be canonically finalized for each and every participant.
What? Sure you can. All you need is confidence in the current owner. You don't need the whole history. Can you imagine the poor store clerk trying to say "sorry sir I can't accept that $20 bill unless you can name every prior owner in order".
Not sure if you're being deliberately obtuse here but this isn't an issue with the cadence of real estate transactions. Real estate ledgers do not need to support HFT.
Never said you need to store the whole history at all times, i said it must be established in canonical way. Storing latest state is just fine. Event Sourcing works this way too, and allows caching recent state.
> Blockchain is unnecessary complicated, for example, it has mining
depends on configuration, you can make any traditional web service replicated (replication is one and only thing that protects data in decentralized ledger, same as DNA is stored in every cell) using something like CometBFT on top. Mining/PoS or VM - all optional.
When working on a project https://github.com/xlnfinance/xln (a financial account network between entities) I stumbled upon a problem that you need a way to emulate a real network deterministically. Then i realized every blockchain is just replicated state machine so why dont we encapsulate every user node into Runtime->Entity->Account hierarchy of 3 state machines. Each outer machine fully controls the inner one. Like "blockchain inside blockchain" with different consensus modes.
Then I googled for "hierarchical state machines" and found statecharts. These two ideas are somewhat similar so here are my 2cents. Imo more software should use hierarchies of state machines to fight the worst class of bugs with non-determinism.
Things programmers believe. It's interesting how some knowledge fundamentally assumed by default. For whatever reasons, the notion is widespread. You're a programmer? Therefore you must know JS, SQL, Bash and Python. In practice, what I've found after decades working with various teams - most programmers have pretty inadequate knowledge of any of these things.
