semanticc

Actually, only the demo car up front and close had different wheel caps. The car that accelerated was similar looking than the one that flew.

It was a clearly different unit, look at the wheel caps.

Write schema/data migration files [with agents] in version control and deploy those deterministically (after review).

I don't want to sound offending, but if that is your own writing style, it makes sense why AI writing resonates with you.

That's not an effect. As both in the case of a dividedend and a stock buy back, the company's market cap drops by the amount of cash that's being distributed out, creating an identical re-buying situation in market cap-weighted index funds. Stock price itself is irrelevant for index fund rebalances (unlike for shareholder returns).

> So for my definition of “everywhere,” with the caveats mentioned above, the following features work everywhere. YMMV.

  .
  ^, $
  […], [^…]
  \*
  \w, \W, \s, \S
  \1 - \9 backreferences
  \b \B
  ? + 
  | alternation
  {n,m} for counting matches
  (...) capturing

Except that these don't work in macOS/BSD sed (even with -E flag):

- \w, \W, \s, \S - need to use POSIX classes instead: [[:alnum:]], [^[:alnum:]], [[:space:]], [^[:space:]]

- \b - need to use use [[:<:]] (word start) and [[:>:]] (word end) instead

- \B - (not a word start/end) no alternatives

It's not documented, but unfortunately neither of these re-signs the commits even if GPG signing is configured. They are based on `git replay`, and that doesn't sign either (at least yet).

How/why did it consume more tokens?

I think the script would be named as `#` so that it can be called via `\# mycmd` instead of `\\# mycmd`.

Unless you disable cursor blinking because you find it annoying (like I do).

Node 24+ does respect HTTP_PROXY when NODE_USE_ENV_PROXY=1 is set.

Do you have an example of this in mind where the known "tit for tat" strategy falls short?

Linux is not developed in GitHub.