Uh, the idea of democracy is not that voting reveals universal preferences or something. It is ok to disagree with whoever gets elected, and continue working towards an alternative you believe to be better. In fact, democracy depends on that; otherwise, why not have a single election with no term limits? There is supposed to be ongoing difference of opinion.

> I also find it difficult to reconcile not using AI for weapons.

You can't reduce "AI for autonomous lethal weapons" to "AI for weapons".

Your comment seems to be whataboutism. The article was not an essay trying to prove that he knows the secret to being maximally effective at politics, or whatever it seems you were expecting?

Then it's good that it allows both modification and using it to run a business?

> This “users are obligated ‘give back’ the moment they make money with the gift they were given” is nonsense

But they are under no such obligation! They can make all the money they want and give nothing back. They can even modify the software to better serve their business. The only restriction is that if they do so, they have to make their modifications available. Which means they're way ahead of where they were before being given the initial software; why do you feel a software developer who decides to give the world a gift should be restricted in what gift they're giving? "Thanks for the chocolate, but the bar was too small so I didn't have enough left over for my kid to try some. Why do you hate my kid?"

> A business making money using free software doesn’t take anything away from the releasing organization.

First, that is false. They could damage the market for the original software. (And if they don't modify the software, then there's no problem in the first place.)

Second, why are you so hung up on the "making money" part, when that is explicitly allowed by the AGPL? It's just kind of bizarre -- it's a license that says over and over that you can charge for everything related to it, and you're complaining about it being hostile to people who want to charge money for things.

Thinking about it, I'm wondering if this is genuine confusion and you don't know what the AGPL is? If so, maybe start by searching for "charge" in https://www.gnu.org/licenses/agpl-3.0.en.html . It has nothing against "using it to run [a] business". There is no "moment they make money with the gift" that changes anything: you are explicitly allowed to charge for anything you like -- distribution, usage of the service, support, whatever.

Those aren't public goods, they're private goods. The difference is already apparent, and will become more so over time. But yes, they are "goods"; they have a lot of value.

I'm less interested in punishing the past theft that enabled these goods, and more worried about the ongoing damage they are doing to the ecosystem that birthed them. Good artists copy, great artists steal, but if a community is wholly dominated by these "great artists" then it will not survive as a community and will cease to produce anything worth copying let alone stealing.

Aside from fair use, yes it is.

> If I draw The Simpsons on a piece of paper - whether or not I used AI to create it - it's not copyright infringement.

Only because of the fair use doctrine, which is limited. If it damages the market for the original, then a court could definitely declare it to be infringement.

> Copyright infringement is if I tried to sell that Simpsons work as my own, putting up for consumption and reaping the monetary benefits.

No. Copyright infringement requires neither sale nor misrepresenting a work as one's one. It also covers derivative works, not just perfect duplicates. Copyright covers reproduction and derivate works and distribution/performance -- you can get in trouble for just one of those. Taken strictly, that would be a horrible world, but fortunately the fair use doctrine weakens those quite a bit. On the flip side, if AI reproduction destroys the original markets -- as it is quite obviously doing right now -- then it's going to have a reckoning at some point, given how its legal status is completely based upon getting a free ride by claiming fair use.

I think Google's AI results are probably the prime example here. Those results are often quite good, and starve off the visits and hence revenue stream of the sites where the results are sourced from. Additionally, there's no way to robustly attribute that information anymore either; those links were already broken pre-AI by freeloading aggregators. So potential information producers can't afford to host their valuable information since they will pay proportionally to their information's value (as translated into bandwidth).

But it's tricky. If you charge AI companies proportional to the damage they do, then you need to assess that damage and you'll be caught in a no-win cat & mouse game where the AI companies outsource the damage and you try to track it back to them. They win if they bump their revenue, but they also win if they conceal the damage. (Just like companies can use shell companies, bankruptcy, and asset-only purchases to avoid Superfund responsibility.) If you charge proportional to revenue, then there aren't conflicting incentives; companies win by increasing revenue full stop. But I do agree that this shouldn't just apply to the big companies; distillation / model extraction (adversarial or not) should not be a way to avoid fees.

Though what really seemed off to me about the proposed solution was the use of the fees (to pay Americans, no less!) Perhaps upcoming essays will justify this more, but to me it seems like those fees should be applied directly to the health of the ecosystem. It should be used to fight pollution, in this case AI slop overtaking the Web. It should support the value creators, eg open source developers being overwhelmed by the AI tsunami. It should go towards serving and moderating online communities that create the very value that the LLMs are trained from. In theory, paying a whole bunch of Americans a trickle of blood money will end up going towards these purposes, but I'm very skeptical: first, the benefit will be very diluted. Second, it's more likely that the excess money will end up in Google or Amazon's pockets. The whole system is already set up to route any advantage to the big players. The payments are at least as likely to damage the ecosystem as they are to support it. They would just feed the capitalistic wolf and further reinforce the setup where monetizers win and value creators lose. If you could magically route the money to value creators, that'd be great. But you can't.

It'd be ok to pour money into a bucket if it had a small hole or two, but pouring it faster into the sieve we have now is not going to help anything.

But I think it would be vastly more difficult to grind two massive stone blocks against each other than to just ram one against the other. Not unless you stacked them, anyway, and if you stacked them I'm not sure if you could move the top one side to side in order to do the grinding. Maybe with some kind of grit, I don't know. Still seems harder.

Also, grinding methods end up removing more material (bad for teeth!), and I would expect more overall physical work to be done in order to remove that material (bad for massively heavy stone blocks).

As for making them flat, that seems unnecessary to me. But then, I'm not a pharaoh. (Even for a pharaoh, it seems like only the seems would need to be straight. Nobody could tell about the faces after assembly.)

Then again, after some quick researching, it seems like there's a good chance that the well-fitting blocks (which are not all of them) may have been cast out of a concrete-like slurry, not hewn.

My dentist is pretty good at doing this too, by putting marking paper between my teeth and having me bite down. I wonder if a similar technique could be used:

Have the blocks close together, constrained to only move on a single axis by rails or whatever. Drape a thin sheet of material over one of the blocks, the non-moving one (perhaps it's an already-placed one?) Maybe it's something that visibly shows when it's crushed, or maybe it's coated with the blood of the powerless. Smash the other block into it. Pull them apart and look where they made contact. If it's mostly everywhere, done. If not, grind down or chip out the parts that touched. Repeat until you run out of innocents.

To do the very last block, you'd have to meld two sides, remove a block, fix up the other side, and then put it back in. Which might make this testable.

But I'm just pulling stuff out of my nether orifice.

> I really don't see the issue with local entities like a school board having some say in material that is available in a school.

Then you prefer a low-trust environment. I prefer a high-trust environment. A librarian shouldn't be putting 50 Shades of Grey on a grade school shelf to begin with. If they are, then you should be replacing the librarian, not micromanaging them. Book selection is their job. Let them do their job or don't; don't allow them the authority to only do half their job.

> But a library acting like they are doing some brave act of resistance by putting out a stack of books that are widely available...and saying they are "banned books, this is banned books week, look at all the books that have been banned!" when really they are books that a school board in wisconsin said shouldn't be in an elementary school library because the sex scenes are not appropriate for 7 year olds seems really silly to me.

Again, that's a "replace or reprimand the librarian" problem. It's not meant to be a brave act of resistance, it's information to say "these books have been banned, look at them so you can better understand what books people want to ban and why". And obviously, it's more interesting than "these are books where the 3rd letter in the title is T" and so it garners more attention, but it's no more than that. If they're including one that was banned for dumb reasons as in your example, then that makes it a dumb display (and an inappropriate one if the display is also in a library for 7 year olds.)

Obviously, the OP is not the librarian, and is aiming for an act of resistance, so my argument mostly doesn't apply there. Though the part about choices having the potential of being dumb still does. The set of books that have been banned somewhere or other is quite large, it's not like it would have any meaning to have a display of all or even a random selection of them. That's a strawman. You're going to curate based on some metric.

If you went the other direction and didn't worry about it being noticeable, it would be kind of a fun project to break up a book into a series of QR codes. A scavenger hunt, with each code's text ending with a clue of where to find the next?

> What it should do is ensure some things not relevant to Half-Life 2 were not done, thus getting better performance for this game in particular, but there is no guarantee that same optimizations work for other applications or games, so one should not expect an overall improvement.

I can't quite parse this. Yes, there is no guarantee that the optimizations will work for another game, which is precisely why you can expect an improvement with hl2. With non-hl2, you may get an improvement, you may not, and you may get incorrect behavior.

Everything else is not the same, but hl2 doesn't use the stuff that's different.

Suggestion: we should all shift our terminology, and in particular make heavy use of phrase "...and it cost N lines of code". And say what we spent those LoC on.

"I implemented new feature X, and it only cost 200 lines!"

"That bug was brutal to figure out, but in the end it only cost 6 lines of code."

"It was doing something in case X that it didn't do in case Y, and it turns out that the distinction wasn't even needed. So I fixed the problem and saved 20 lines of code at the same time!"

Lines of code are a price you pay. We don't go around bragging about how we spent $200 without any mention of what we purchased with that money. Why do we do that with LoC? "I had to pay an extra $200 because I signed up late" and "I only paid $200 for my hand-painted artisanal pottery lamp hanger. Factory-made ones cost upward of $1200 on Amazon!" are two very different statements, and map to exactly the same distinction in code.

Interesting writeup, but:

No, anonymous AI author. Your process is using that memory, for its allocator. Features like lower-latency allocations don't come for free, even when they turn out severely suboptimal for your particular case. Your code isn't using that memory, but a support library is. It is very much in your process.

I want to go back to being dumb and naive. Give me the blue pill, please!

> I've since rewritten nearly 100% of the prose in the analysis with my own, more inflammatory and verbose style. I also intentionally left in my natural mispellings and typos, to prove it was me.

Thank you thank you thank you. I would love to be able to describe how hard it was for me to think about the actual evidence you're presenting when reading about it through the AI writing, but I suspect it's one of those things where it bothers you or it doesn't. If you'd like to empathize, maybe I'll give it one try: imagine an otherwise solid PhD thesis written in crayon. The facts and evidence and reasoning are unaffected, but it's just so hard to take it seriously.

Anyway, with the rewrite I don't have to battle my kneejerk reactivity nearly as much.

I'm no expert like she is, but based on what I know, I agree with your wife on the statistics. That style of analysis is going to be the best you can do with the data available. It's an accepted way to stretch data without being too dependent on an assumed distribution. It's a good analysis. I still don't come away with the conclusion that concerns about AI code maintenance are necessarily overblown, but that's fine. I think your analysis project is a very solid contribution, and it's a hell of a lot more evidence-based than the rants people were posting.

I am pretty insensitive to AI writing. I have never commented before about something sounding like AI, because mostly I don't notice. But this was so over the top that I spent the whole article trying to decide whether it was an intentional parody of AI writing style.

This article's language is not en-US. It's not en-BR. It's en-SLOP.

Yes, that was my clumsy attempt at AI parody. Here's another: this article doesn't just have AI tells. It is AI tells.

Every sentence is saturated with AI style. Perhaps the author so AI-indoctrinated that they can't see this? It doesn't read as even vaguely plausible human writing. Which is mightily ironic given the thesis of "AI generated stuff is just fine, m'kay?" The writing style does more to defeat its conclusion than the analysis itself.

As for the substance of the analysis, it seems pretty good to me but I see some flaws that weaken it a bit.

The presence of "The Outlier Nobody Noticed" proves nothing and deserves no more than a passing mention. A random release introduced way more bugs than the Claude-containing releases. That provides evidence that Claude doesn't introduce more bugs only if your hypothesis is a very naive "AI is the only thing that can ever increase bug introduction rates."

The whole analysis has very limited data. It's necessarily based off a single pair of releases at the very end of the chronological timeline. You would never be able to reject a null hypothesis based only on that, so it's even less sound to present it as proving the null hypothesis. (By the same token, it would be incorrect for critics to claim that it proves their point. Did anyone claim this, though? The heated complaints seemed more based on priors about AI code.)

"The critics' claim is a simple comparison: did the rate go up?" That's reductive. For one, these releases are known to be in reaction to a flood of (AI-discovered!) security reports, which is a novel situation and in fact is a huge confound to anyone arguing about what those two releases mean -- they're both heavily AI-written, but in response to an unusual situation. When the samples are only drawn from a distinct scenario, statistic analysis can only speak to the quality of code in that scenario.

Also, another reasonable hypothesis could be: AI-written code has bugs of a different flavor that bothers users more. It's optimized for passing tests and convincing people and AIs that security holes are closed, which means other considerations like preserving functionality can more easily be regressed as compared to if humans were doing it. (If true, it still doesn't support the claim that depending on AI code is a catastrophe, fwiw.)

I'm not arguing the conclusion is wrong. I'm saying the analysis proves far less than it claims to. As for whether it's a debacle for rsync to become dependent on AI code generation, I think that's a reasonable debate to have but it's not going to be resolved this reductively.

Whether you agree with that argument is another question.