What the internet is saying about Vibe Coding

What the internet is saying about "vibe coding"

🟢 Supporters

• •Non-developers are building real tools. An Ask HN thread on "internal vibe-coding apps" includes a powerline construction firm where non-devs vibe-code planning apps. These apps connect to the land register and mail affected landowners automatically. Another commenter has heard of non-engineers vibe-coding dashboards and deploying them [3].
• •Hobbyist and hardware communities are adopting it. Coverage describes vibe coding "turning the music gear world upside down" through custom firmware [4]. Another piece says people are "vibe coding their way to better TVs" [8].
• •It is seen as a lever against incumbents. The ArtCraft/Adobe discussion drew the most HN engagement (71 comments). Some commenters used it to attack Adobe for "decades without any real innovation" and "hostile dark patterns" around subscriptions [5].
• •Tooling is being built around it. A "Meta Vibe Coding Agent" (Trama 0.1.1) was shown on HN and got a friendly "Looks neat" reply [1].
• •One user embraces the label. They describe it as "a random thought and test to see what I can produce quickly… Could be trash or could be gold" [2].

🔴 Skeptics

• •The ArtCraft project is criticized as overhyped. One commenter asked whether an open-source vibe-coded creative suite is worth cheering and answered "No." They said such projects "suck the oxygen out of the open-source ecosystem" for more credible tools like Photopea, GIMP and FreeCAD. They also said the author promotes it "HARD" despite being far from feature parity [5].
• •Design quality is a weak point. One commenter argued that AI neglects design beyond "rounded corners, stock buttons and forms," and that when it works it is "by accident" [3].
• •Honesty and disclosure are an issue. A GitHub issue titled "This project is AI generated" argues a port was "heavily AI-assisted" and that what matters is honesty, not AI use itself. It drew 14 comments and 10 reactions [11].
• •Open-source projects are setting guardrails. cp2k is adding docs hints on AI contributions, stressing contribution quality and "human involvement and connection" while saying it isn't "unfriendly" toward AI coding [13]. Resonite has a draft generative-AI policy [18].
• •Practitioners are looking for alternatives. A VS Code extension is pitched as "Stop Vibe Coding. Enter Guide Coding" [6]. Another thread asks whether vibe coding is bad for SaaS projects, but the snippet shows no substantive answers [9].

⚪ Neutral Observers

• •The term itself is contested. An HN PSA says it has become "insulting and a bit of a slur." A reply says it "accurately describes how most people use AI for code generation" and that careful, test-driven users are a small minority [2].
• •Mainstream media is treating it as an industry shift. Kotaku covers vibe-coding hitting games "like an avalanche" [7]. The New Yorker looks at China's "vibe-coding capital" as a lens on the AI boom [10]. The snippets don't show the stance of either piece.
• •Agentic AI workflows are generating friction, though not always under the "vibe coding" label. The VS Code Copilot feedback issue has 232 comments and 295 reactions, and concerns granular control over agent-made changes [15]. Other GitHub items show heavy AI-agent use, such as Claude missions [16] and model test runs [12]. Their relevance to vibe coding is indirect.
• •Several GitHub results look like noise. Items such as [14], [17], [19], [20], [21], [22] and [23] don't show vibe coding in their snippets, so I haven't used them as evidence.

Cross-Platform Signals

• •Hacker News is the main venue for explicit "vibe coding" discussion. Ten of the items there are directly on topic, but most have low engagement (0–11 comments). The exception is the ArtCraft/Adobe thread [5].
• •GitHub activity is about AI-assisted work in practice. It centers on contribution policies [13][18], disclosure disputes [11], and Copilot and agent controls [15]. It rarely uses the phrase "vibe coding."
• •There is divergence between the two. HN and media coverage lean toward spectacle and cultural debate: new niches, non-dev builders and the naming fight. GitHub leans toward governance and quality control.

Community Verdict

Vibe coding is widely recognized as mainstream, but sentiment is mixed. Enthusiasts point to non-developers and hobbyists building useful tools, and to challenges against incumbents like Adobe [3][4][5][8]. Skeptics worry about quality, hype, design, and honesty about AI use [3][5][11]. Maintainers are responding with policies rather than bans [13][18]. Even the label is disputed, as some see it as accurate and others as a slur [2]. The data are thin, with low engagement on most items, so this is a snapshot rather than a firm consensus.

---

Based on Hacker News + GitHub data from the last 30 days, researched with last30days by Matt Van Horn.