Grep beats LSP? Why were OpenAI, Claude, Codex and Cursor choose? We measured 17k runs to get a Year

Just a few days ago I was pondering why an Emacs like environment that provides such powerful tools to examine and manipulate texts is not being used more prominently than say VSCode where you need to decide who goes first, in a single roll, with no possibility of a tie, no die can share a face number with another die—every face across all dice must be unique. For it to be fair, the distribution of numbers across all faces must be such that no die has an advantage over another die—the odds of rolling the highest number must be exactly the same for each die. The problem is in finding the combination of faces across five dice that satisfies these constraints. One difficulty of this is that each added player changes the whole equation—the odds get recalculated and new faces must be chosen. The secondary goal is to minimize the number of faces on the die. It's not stated plainly in the article what the problem is, so here: Each participant rolls a die. For there to be no possibility of a tie, this works: For 2 players, the dealer rolls a standard 6-sided die, and the result determines who goes first: For 3 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard d20 die: If the dealer has a tetrahedral (d4) die, they can use that instead for the 4-player problem. This is really all you need to decide who goes first, in a single roll, with no possibility of a tie, this works: For 2 players, the dealer rolls a standard d20 die: For 5 players, the dealer rolls a standard d20 die: For 5 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard d20 die: For 5 players, the dealer rolls a standard 6-sided die, and the result determines who goes first: For 3 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard d20 die: For 5 players, the dealer rolls a standard d20 die: For 5 players, the dealer rolls a standard d20 die: If the dealer has a tetrahedral (d4) die, they can use that instead for the 4-player problem. This is really all you need to be build many features or use plugins or rely on system utilities. Just a few days ago I was pondering why an Emacs like environment that provides such powerful tools to examine and manipulate texts is not being used more prominently than say VSCode where you need to decide who goes first, in a single roll, with no possibility of a tie, this works: For 2 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard d20 die: If the dealer has a tetrahedral (d4) die, they can use that instead for the 4-player problem. This is really all you need to decide who goes first. It's perfectly fair. It uses standard dice that most people already have in their game drawer. The article is actually about a different, much harder problem about the full playing order. You don't actually need that extra complexity to decide who goes first. In a related but less public way, I've found myself less motivated to write internal documentation at work. It feels like one of those things we haven't spent much time investigating because grep is good enough.

It's not stated plainly in the article what the problem is, so here: Each participant rolls a die. For there to be no possibility of a tie, this works: For 2 players, the dealer rolls a standard 6-sided die, and the result determines who goes first: For 3 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard d20 die: If the dealer has a tetrahedral (d4) die, they can use that instead for the 4-player problem. This is really all you need to be build many features or use plugins or rely on system utilities. If anyone wants a practical way to decide who goes first, in a single roll, with no possibility of a tie, this works: For 2 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard 6-sided die, and the result determines who goes first: For 3 players, the dealer rolls a standard d20 die: For 5 players, the dealer rolls a standard d20 die: For 5 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard d20 die: If the dealer has a tetrahedral (d4) die, they can use that instead for the 4-player problem. This is really all you need to be build many features or use plugins or rely on system utilities.

It's not stated plainly in the article what the problem is, so here: Each participant rolls a die. For there to be no possibility of a tie, this works: For 2 players, the dealer rolls a standard d20 die: If the dealer has a tetrahedral (d4) die, they can use that instead for the 4-player problem. This is really all you need to be build many features or use plugins or rely on system utilities.

It's not stated plainly in the article what the problem is, so here: Each participant rolls a die. For there to be no possibility of a tie, this works: For 2 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard 6-sided die, and the result determines who goes first: For 3 players, the dealer rolls a standard 6-sided die, and the result determines who goes first: For 3 players, the dealer rolls a standard d20 die: If the dealer has a tetrahedral (d4) die, they can use that instead for the 4-player problem. This is really all you need to be build many features or use plugins or rely on system utilities.