I got into #FLOSS because it was a community-driven approach to making computers empower people. Now, #opensource means "free training data for someone else's LLM."

I could ask, "What is the future of open source software," but I think that's the wrong question. I'd rather contemplate what community-driven, human-centering computing can look like in the era of scraping and slop.

@jrbe @robin Unfortunately, I'm currently at the viewpoint that open source is dead, and we just don't know it yet.

@ramsey @jrbe Oooft. I'm gonna have to sit with that one for a bit. It does make me wonder. Open source _has_ always been a hack on broken and corrupted intellectual property laws... Reimagining it entirely starting with James' question feels proper.

. o O (It feels like we're entering a nexus of change as many systems we've relied on buckle under the weight of unsustainable things, including greed. I wonder what kind of world we'll usher in next. Anything feels possible, good or bad...)

@robin @jrbe I waffle on this day-in and day-out. The other day, I was discussing SDKs with a colleague, and I said, “Why do we need SDKs anymore? Folks’ll just ask AI to build the integration for them.”

My colleague spent a few days reading the current blogosphere views about this and found that most seem to agree that SDKs are now more important than ever because, when asked to do something, LLMs will find a pattern and use it, and your SDK needs to be the pattern.

@ramsey @jrbe That makes sense to me! My other half is giving a talk touching on that at North Bay Python this year — though he centers on frameworks, wherein there isn't going to be a big corpus because the idea is to craft just a few per language. SDKs strike me as similar in that way, perhaps even more rarefied.

Not the kind of thing an LLM lends itself to, even if it was ethically sound and grounded in humanity.

I'll be glad when we get to the real table flipping moment with all this!

@robin @jrbe You and me both!