> Is the energy usage so different between local and cloud inference?

In throughput mode for agentic loads, the energy usage (tok/s/MW) of the new NVidia Vera Rubin hardware is 30x lower than that of the B300 and perhaps 450x lower then the H200 was, which in turn is hundreds of times lower than the inference for single users at home in any non-data-center hardware. It feels like comparing the momentum of an ant to the momentum of an elephant.

This doesn't have anything to do with water usage? The rationale of banning it is that it's copyright status is ambiguous and at the least unethical, it produces lower quality code, and it stifles new developers from getting involved.

People want to ban LLM contributors not because of energy usage, but because AI generated code is unmaintainable and the people who generate it tend to engage with others in domineering and brazenly manipulative ways.

Debian is huge - that's why so many other distros use it as a base!

So, yes, all those packages are maintained either by an individual Debian Developer or a team of them.

There are third party repos, but they're (currently) neither as widespread nor as commonly-used as those for other major distros. This vote won't affect them, and you might potentially expect to see their use grow if one of the harsher options in this GR were to pass.

There's not yet any reason to believe that mixing LLM output with your work makes it uncopyrightable any more than hitting enter in intellisense did before that.

I'm curious about enforcement. Are they going to ban packages with a whiff of llm? If so, how will they reliably audit?

It does not appear that normal people can. There is no vote page, no information on how to, and we can only view results.

> and ideally vote for a total ban.

If a total ban were to happen, wouldn't that make Debian a target for hackers who can use LLMs to find vulnerabilities?

How would Debian keep up with the influx of AI assisted 0 days?

Given almost all people here cannot vote, does this mean you posted non-AI-generated slop?

Wouldn't it be better to reduce slop, no matter how it was produced, instead of only AI-generated contributions, including non-slop contributions?

Are you going to fork kernel? If not then you are just a bunch of stupid hypocrites.

> Posting this because I want people to vote

Irrelevant to post it here then with your reasons because it only concerns Debian developers

The options range from is A to H. It's not yes or no.

Then you cannot use Linux, Firefox, Chromium, Python, Rust, LLVM and so on. Hurd can't be used either.

Maybe you have to switch to FreeDOS?

Every non-technical person I know hates genAI and goes far out of their way to avoid it.

> it will be ubiquitous and universal in adoption

[[citation needed]]

Which is gonna be tricky as I am confident you don't have a time machine.

I think generative AI as a whole is a total scam. It has uses, but not many, and outside of translation, not good ones... and yet, it is running at truly epic financial losses. Multiple trillions of dollars are being pumped into this.

I think the next AI Winter, the 3rd big one, is coming very soon.

There's going to be a market crash to dwarf the dot-com crash and 20087 financial crisis (both of which I worked through as an employed adult), and a lot of the current tech industry will be wiped out.

I've watched that happen before as well.

I am quite looking forward to it. I have no stocks or shares in anything anywhere, few savings, no loans, no debt... but all my immediate family own their own homes outright, and I am close to retirement age.

Let it all burn.

> the average non-technical person uses AI daily

Citation needed.

"Having one's head in the sand" means being unaware of something; everybody is aware of it. "Conspiracy theorists" is just a slur.

If you have anything substantive to say about it that other people haven't heard, we're listening.

[dead]

It's one thing for a maintainer to use AI, and another to review AI code sent your way. The latter has been proven to be unsustainable, low value, and ultimately a challenge for open source. Everyone acknowledges this problem exists and some corrective action is required to mitigate it.