[Aurornis]

I agree completely. I know everyone is tired of AI accusations but this article has all of the telltale signs of LLM writing over and over again.

It’s not encouraging for the future of a project when the maintainer can’t even announce it without having AI do the work.

It would be great if this turns into a high effort, carefully maintained fork. At the moment I’m highly skeptical of new forks from maintainers who are keen on using a lot of AI.

[bugufu8f83]

>I agree completely. I know everyone is tired of AI accusations but this article has all of the telltale signs of LLM writing over and over again.

I mean, I'm more worried about the AI writing itself than people calling it out.

The AI articles on HN are an absolute disease. Just write your own damn articles if you're asking the rest of us to read them.

[doctorpangloss]

@dang what do you think? Is it a disease? People who make interesting conversation will tune out.

[bigiain]

I'm not Dang, but I agree AI articles are a disease - but with reservations.

In this case, a Chinese developer who's not a native English speaker - I feel is _adding_ to "interesting conversations" not detracting from them but using AI assistance to publish an article like this in readable/understandable English.

I know HN and Ycombinator is _hugely_ US focused and secondarily English-speaking focused. But there's more and more interest in non US based "intellectual curiosity" where the original source material is not in English. From YC's capitalism-driven focus, they largely don't care. From my personal hacker ethic curiosity, I'd hate to miss out on articles like this just because of a prejudice against non English speakers who use AI to provide me with understandable versions.

Having said that, AI hype in general certainly feels like a disease to me. I was noting recently how the percentage of homepage like/discussions I click has gone way down. I remember the days where I'd click and read 80 or 90% of the things that made it to the homepage. These days I eyeroll my way past probably 2/3rds of them because they look at first glance (and from recent experience>) to just be AI hype in one form or another. (I've actually considered building myself a tool that'd grab the first three or so pages and then filter out everything AI related - but the other option is just to visit less often...)

[bugufu8f83]

I'm all for people who aren't native English speakers publishing their thoughts and opinions. But I would much prefer they still wrote down their own thoughts in their own words in their native language and machine translated it. It would be much more authentic and much more interesting--and much more worth reading.

[mahkeiro]

I'm not sure, based on past experiences people are complaining a lot about automatically translated text...

[GCUMstlyHarmls]

I just get my agent to read them for me and present a few options for comments as derived from the vibes of any existing comments. If I time out, it posts a random option, then at the end of the week I get it to summarise all the content I (royal) read and distill it into a take-aways note in my (royal) journal. It's been a huge productivity boost. When ever I think I might want to think about something I just ask the agent to find a topic I (royal) read within some timeframe and have it synthesise a few new dot points in my (royal) journal. I'm hoping to reach 10,000 salient points by the end of the year.

[empath75]

An app that basically reimplements a well documented and tested api is the best possible use case for ai development.

[Aurornis]

I have nothing against a skilled maintainer with attention to detail using AI tools for assistance.

The important part is the human who will do more than just try to get the LLM to do the hard work for them, though. Once software matures the bugs and edge cases become more obscure and require more thoughtful input. AI is great at getting things to some high percentage of completeness, but it takes a skilled human to keep it all moving in the right direction.

I would cite this blog post as an example of lazy LLM use: It's over-dramatic, long, retains all of the poor LLM output styling that most human editors remove, and suggests that the maintainer isn't afraid to outsource everything to the LLM.