Open post Rivermonster @RomanOnARiver@mastodon.social · 2mo ago Replying to @RomanOnARiver@mastodon.social Reading https://www.spurint.org/journal/2026/07/llms-and-xfwl4 where an #xfce dev admits to AI slop vibecoding what may be significant parts of the #Wayland port. This is a really bad precedent to set, this should not be allowed. I'm hoping this trend doesn't continue, but it will definitely lead to actionable responses if it does. #gnu #linux Also, saying "I don't vibe code" then talking about having the AI write code... What is going on?
Open post Rivermonster @RomanOnARiver@mastodon.social · 2mo ago Replying to @malwareminigun@infosec.exchange @RomanOnARiver@mastodon.social is it that you don't see the distinction, or is it that you don't believe it to be meaningful? If truly the former, pretend it's OSS with no AI at all where one maintainer actually reviews and spots bugs in PRs vs. one who just rubber stamps and merges anything. (To be clear, the only reason I replied here is because your toot was in the form of a question. FWIW I would describe my day job as mostly vibe coding these days; before AI most vcpkg PRs were a rubber stamp) @malwareminigun@infosec.exchange it was more rhetorical. In the sort of "Xfce using AI code wasn't on my bingo list for 2026". Now I may have to gear up to switch to something else, I don't know what's out there these days.