On Thu, Jul 2, 2026 at 6:00 AM Xiang Xiao <[email protected]> wrote: > > On Thu, Jul 2, 2026 at 4:40 AM Tomek CEDRO <[email protected]> wrote: > > > Hmm, we just got a good-bad-example, take a look at: > > > > https://github.com/apache/nuttx/pull/19249 - this adds new board > > rpi-pico-2-w but also breaks other areas boards etc. Matteo closed it > > as ai slop right away. > > > > https://github.com/apache/nuttx/pull/19250 - then this PR showed up as > > fix very quickly after, with less issues, focused on the board added, > > and author honestly admitted all code was generated by AI. > > > > > > Thus my response in the PR but also here: > > > > > @xiaoxiang781216: We need accept the trend: all developers will utilize > > AI to generate material (code, commit, documentation, pr) sooner or later. > > > > @xiaoxiang781216 I agree with @linguini1 here, and looking at the > > mailing list, most of the community - we want to keep NuttX a project > > developed by a community of passionates, professionals, and > > enthusiasts. > > > > "all developers will utilize AI to generate material (code, commit, > > documentation, pr) sooner or later" - yes we cannot avoid that, but we > > do NOT need to "accept the trend", we may just acknowledge the problem > > but not become part of the problem :-) > > > > This is similar to "rewrite everything in Rust" "trend" - we may > > acknowledge the problem and still not become part of the problem :-) > > > > Let people rewrite everything in Rust, but from scratch, away from > > here. The same with AI :-) > > > > > > I agree with Matteo that we should avoid AI slop. We had many bad > > examples already, costing us time and energy that could go intro > > something more constructive. Many Open-Source projects acknowledge > > this problem and do not want to be part of the problem. We want "our" > > projects to stay "ours" in terms of fun, code, mistakes, learning > > curve, experiments, and the overall the community of enthusiasts. > > > > What is the fun in rewrite-whole-NuttX-with-a-single-click for me ?? o_O > > > > > Where do I say rewrite everything with AI? The following PRs are generated > by AI: > !include/fcntl.h: align open flags with Linux values by xiaoxiang781216 · > Pull Request #19238 · apache/nuttx > <https://github.com/apache/nuttx/pull/19238> > include/fcntl.h: remove O_RDOK/O_WROK aliases by xiaoxiang781216 · Pull > Request #19231 · apache/nuttx <https://github.com/apache/nuttx/pull/19231> > libc/grp: add getgrouplist() by xiaoxiang781216 · Pull Request #19183 · > apache/nuttx <https://github.com/apache/nuttx/pull/19183> > drivers/serial: add job-control TTY ioctls by xiaoxiang781216 · Pull > Request #19184 · apache/nuttx <https://github.com/apache/nuttx/pull/19184> > fs: widen ino_t to uint32_t and add d_ino to struct dirent by > xiaoxiang781216 · Pull Request #19179 · apache/nuttx > <https://github.com/apache/nuttx/pull/19179> > arch/sim: replace macOS C++ constructor runtime hack with post-link patch > by xiaoxiang781216 · Pull Request #18886 · apache/nuttx > <https://github.com/apache/nuttx/pull/18886> > !sched/clock: drop CONFIG_SYSTEM_TIME64 / CONFIG_HAVE_LONG_LONG / > CONFIG_LIBC_LONG_LONG and sclock_t by xiaoxiang781216 · Pull Request #18840 > · apache/nuttx <https://github.com/apache/nuttx/pull/18840> > tools: replace showstack.sh with stackusage.py by xiaoxiang781216 · Pull > Request #18538 · apache/nuttx <https://github.com/apache/nuttx/pull/18538> > !sched: drop CONFIG_SYSTEM_TIME64 / CONFIG_HAVE_LONG_LONG / > CONFIG_LIBC_LONG_LONG and sclock_t by xiaoxiang781216 · Pull Request #3468 > · apache/nuttx-apps <https://github.com/apache/nuttx-apps/pull/3468> > apps: drop redundant 64-bit casts on tv_sec/tv_nsec arithmetic by > xiaoxiang781216 · Pull Request #3476 · apache/nuttx-apps > <https://github.com/apache/nuttx-apps/pull/3476> > Replace O_RDOK with O_RDONLY after alias removal by xiaoxiang781216 · Pull > Request #3566 · apache/nuttx-apps > <https://github.com/apache/nuttx-apps/pull/3566> > apps: Replace O_RDOK with O_RDONLY after alias removal by xiaoxiang781216 · > Pull Request #3568 · apache/nuttx-apps > <https://github.com/apache/nuttx-apps/pull/3568> > apps: Fix O_ACCMODE bitmask checks after Linux flag alignment by > xiaoxiang781216 · Pull Request #3572 · apache/nuttx-apps > <https://github.com/apache/nuttx-apps/pull/3572> > All of them either fix the problem, or add new functionality. > AI is a powerful tool just like a knife, whether it can make a positive or > negative impact depends on the user. > The excellent engineer could do a wonderful job with AI. > I am still the owner of the above PRs since AI can't generate these PRs > without my thought and instruction.
Hello Xiang, yes you are aware user that knows the code base perfectly and use AI as your supporting tool, there is nothing wrong with that! :-) We are talking about many blind copy-paste of the results. We would like to put some sort of notice or set of rules that would prevent such situations. We want to create a good community where people think on their own and help each other. There seems to be a trend "lets rewrite everything with AI" just as "lets rewrite everything in Rust" and I was referring to that. For me this is almost the same problem and we not necessarily want to be part of that problem. We may acknowledge the problem but we do not have to agree to that and thus not become part of the problem. Also I have no problem with "rewrite" in "Rust" or "AI" when its done from scratch, but leave working existing projects alone. In the long term this is destructive and created unmaintainable projects, thus my resistance here :-) Another example here - security bugs are reported using AI tools, but rarely fix is proposed, what would make things a lot smoother. I know both sides, it would be nice to address them both. -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
