I had the same exact thought. It's implied, but I don't think the article explicitly states that the content produced by the think tank has minimal or no human involvement.
Reading about the batch optimization, I suspect there'll be trouble ahead for implementing window functions, unless those details were dropped for simplicity.
How so? Window functions work exactly the same way. Postgres processes them one row at a time, and you can batch them the same way as you would with sum.
Window functions do make parallel queries more difficult, but that's a different story.
I guess regardless of if the calculations are batched or not, all the rows would have to be processed before the window function results could be determined.
The possibility of competition, and an existing proof of concept, could motivate the Postgres team to pursue performance initiatives that they otherwise wouldn't.
I've been vibe coding a cross platform desktop app targeting bird photographers, that uses photo metadata and vision ML models to generate an eBird checklist formatted CSV for importing. It can detect and classify many birds in a single photo as well as individual birds.
https://github.com/jkanethird/rackery
reply