Hacker News Reader

Comment by nalekberov | Hacker News Reader

> Everyone is still learning how and how much AI should be used and we shouldn't be too harsh on opensource developers.

The main problem with using AI in open source software is that millions of people rely on your code, but you risk exposing them all to something unverified.

View on HN

If millions of people are relying on free software, that's their problem, isn't it? The maintainer has zero obligations to them, and they are not entitled to anything. If they want commercial support or SLAs, they could tender an offer, or else they can fork it and maintain it themselves. I think the maintainer here is being a silly goose but it's their right to be as silly as they want in their own repo.

Yes, you risk reputation and still need to be careful. One way to try to mitigate is to write tests. Which is what rsync project is doing, too. But there's only so much you can catch alone.

And BTW, you're not distributing to millions of people as an author of the code.

There are distributions maintainers between you and the world, which can also intervene, and are responsible for what they distribute, build testing on many configurations/architectures/versions - and can decide to revert to protect users, etc. And often do.

FOSS authors themselves can't be expected to keep around outdated systems from 5 years ago just to test build compatibility, in 8 different architectures that someone may want to build their code with.

Very few projects have as comprehensive testsuite as say sqlite. You can never cover everyting, so the beauty of FOSS is that someone will come and tell you and send you a fix for their special system, and now everything is again fine for that one special person, or distro maintainer.

Well maybe we shouldn't then? Before LLMs some not just clueless but also malicious rando could've send a PR too. And the maintainers might've gotten burned out any and just said f-it and merged stuff randomly. I don't see how AI changed the calculation here much.

No reasonable maintainer would recklessly merge something he/she hasn’t reviewed. Well, those who blindly accept whatever AI outputs… perhaps it’s time for them to find another job.

Just because one offers software for free doesn’t mean there shouldn’t be standards.

That's an interesting use of the word 'job'. How much is the rsync maintainer paid?

My bad, I meant profession.

Same issue there. A profession is an occupation that you get paid for doing.

AFAIK the rsync maintainer does it for free. And he mainly seems to be getting abuse in return for that service.

> Same issue there. A profession is an occupation that you get paid for doing.

Wrong, a profession is an occupation that requires specialized training or qualifications. This means one can have a profession and still not get paid.

> And he mainly seems to be getting abuse in return for that service.

What abuse you are referring to?

If you want to go down that semantic route, then being an open source maintainer clearly isn't a profession, as it requires neither specialized training nor qualifications!

In terms of abuse, I was thinking of this issue thread: https://github.com/RsyncProject/rsync/issues/929

> If you want to go down that semantic route, then being an open source maintainer clearly isn't a profession, as it requires neither specialized training nor qualifications!

Open source software maintenance without qualifications? I hope you understand how disastrous it would be for serious software like rsync.

I should think most open source software is maintained by people without any special training or qualifications. And would you expect to obtain the services of, say, a highly qualified plumber or electrician for free?

It might be more useful if qualifications were required before people were allowed to complain about open source software on internet message boards. That’ll be the day!

Before, there was a chance to spot it (and things like XZ Utils backdoor were rare), now it will be well hidden in the ocean of slop PRs.

You also risk exposing users to any other error you make. That's called a bug.

Unless someone points to vibe coded/hallucinated code causing the breakage or provides clues that might indicate unreviewed slop code being committed and shipped, I'd hold my horses.

Reply on news.ycombinator.com