It is not even close to sufficient. jj fix only executes the command on one file at a time (only the changed files) so it can't work on anything that has linter semantics.
jj does this for performance reasons. They don't want to perform a full checkout for every rebase action. This is simply something I disagree with
> jj does this for performance reasons. They don't want to perform a full checkout for every rebase action.
It's true that `jj fix` can be faster by not touching the working copy, but we also want a `jj run` command for the linter feature (https://github.com/jj-vcs/jj/issues/1869). It's just not done yet.
jjui is definitely the best contender ive seen for a jujutsu ui. although, with the ergonomics of jj, and a decent merge editor setup like meld, i haven't really needed a ui at all
there's 1,000,000 validators (defined as a public key), but you can run multiple validators per machine. Most estimates that crawl the p2p network to index nodes comes out at like ~20,000 machines
doesn't invalidate your point but it at least shaves off a few orders of magnitude
and a single PG node is not a fair comparison, we're talking 100% uptime global networks. Visa does about 70,000 transactions per second - how many servers do you think they run across their infra?
ZK rollups which greatly compress data on chain without losing security guarantees, combined with temporary storage using data sampling so each node only has to store a small portion of it. The zk rollups are live and support significantly more than 150tps today, and the data sampling goes live in November. There's a lot more work to be done but that puts the major pieces in place.
With a lot of characters/scenarios of a sexual nature. They are the market leader for NSFW LLM experiences. Or maybe it's more accurate to call them "dating" experiences
