noahgolmant

The human has unique context. They may work in a niche domain or they talked to people and observed an unsolved problem. Then they express a potential solution via OSS. It's like product sense. Then they share that with others who find it interesting. The code is a great way to encapsulate the idea. It is usually the result of research and back and forth not a single prompt. It would be way harder to think through or build a solution without AI even if they had context.

I don't really know. Certainly we need a higher bar. The Kafka example in the post may be hyperbolic but I agree it pollutes the space. But we also can't swing the other way and rely completely on out of date proxies. If you ban AI code there will be very little code to see in a year. It'll take time but we'll arrive at new norms. We built semi successful ways to filter content farms in the earlier internet days. The signal has to shift to "did they think hard about this problem" which has some observable properties. Like how they articulate the problem, or why it became important to them.

There has to be room for an AI-driven project that expresses a unique idea, even if there's no community around it yet. Someone has to express it, and from now on that idea will largely be implemented with AI.

> A good use of AI is when it enables people to do something they couldn’t do before, to contribute to a community when they couldn’t before.

I agree 100% with the novel contribution aspect. But there's some nuance there.

For example a project might have no active contributors. It might not be something you can drop directly into your codebase. Neither of those is inherently bad.

As AI becomes more responsible for higher-level planning decisions, the value of an OSS project becomes less tied to visible community activity like PRs and issues.

I notice this in my own work a lot. I might not use that project's code directly. But I think about a problem differently as a result. I often point my agent to existing OSS projects as inspiration on how to solve a problem. The project provides indirect value by supporting architectural decisions, deployment approaches etc. Unfortunately OSS activity doesn't capture this.

I would not extrapolate California results to the rest of the country. Other regions like Northern Virginia or Dallas-Forth Worth dominate current and future data center load. They have significantly different water and land use trends. Of course agricultural water usage is higher in California- it's the top agricultural state in the country. And energy prices are much higher, resulting in a smaller data center presence. State regulations also determine water usage efficiency requirements. So it might differ in less regulated states like Texas.

You may want to look into the PMTiles format and tippecanoe. It efficiently produces pyramidal XYZ tile overviews of vector data. Sometimes this is also done server side via the PostGIS asMVT ffunction, or Martin.

For client side rendering, deck.gl is quite good, also a newer library called lonboard from DevelopmentSeed.