Attack of the Vibe Coded Photoshop Clones
AI-generated “vibe coded” clones of Photoshop are prompting sharp debate over software quality, economics, and ethics. Critics argue these rushed, LLM-built tools are technically weak, legally dubious copies that threaten incentives for professional developers, while supporters counter that open, cheap alternatives are a justified response to Adobe’s subscription lock‑in and years of “enshittification.” Many expect rapid iteration to close today’s feature and performance gaps, raising broader questions about how generative AI will erode traditional software moats and business models.
Perceived quality of vibe‑coded Photoshop clones
- Many find current clones buggy and incomplete (e.g., laggy brushes on large canvases, basic paste bugs, sluggish high‑res work).
- Others report them as surprisingly fast and already “good enough” for casual photo editing or simple “Photoshop‑style” tasks.
- Brush engine quality and performance on huge images are repeatedly cited as a real, hard problem that incumbents still do better.
- Several argue these issues are fixable with more AI‑driven iteration and targeted optimization; critics say architecture is already compromised.
Adobe’s reputation and subscription backlash
- Strong resentment toward Adobe’s subscription model, cancellation penalties, and ancillary “bloat” (Creative Cloud app, license checks).
- Some describe extreme friction when trying to cancel; others suggest workarounds like card cancellation or subscription tier tricks.
- Many frame hostility to Adobe as earned over “enshittification,” not irrational “hate campaigns.”
Economics and sustainability
- One side: spending thousands on tokens to clone a $200/year product is irrational, and clones lack support and business backing.
- Other side: one‑time vibecoding creates a free, open alternative for everyone; cost amortizes across all users and resembles “charity.”
- Token costs via subscriptions may be far lower than API prices, making experimentation cheap.
- Skeptics question long‑term maintenance without paying customers; proponents expect community plus AI tools to sustain development.
AI development dynamics and future trajectory
- Debate over the “three human years in a few AI days” framing: some see it as proof clones are already “mature and bad,” others note velocity means they can quickly iterate and fix pain points.
- Several highlight verification, testing, and architecture as the new bottlenecks, not code generation itself.
- Many expect rapid improvement and broader disruption of SaaS and complex desktop apps; others predict most high‑profile clones will be abandoned.
IP, legality, and ethics
- Some analogize to past software and modding IP disputes; others note cloning UIs/features is generally legal.
- Ethical tension: discomfort with AI “trained on everyone’s work” vs. schadenfreude that a disliked incumbent is being undercut.
Use cases and user segments
- Casual and hobbyist users often find open source or vibecoded tools sufficient and appealing, especially on Linux.
- Professionals point to file‑format fidelity, performance at extreme resolutions, advanced tools, and reliable support as Adobe’s remaining moat.
Tone of article and thread
- Many see the original article as emotional, defensive of Adobe, and weakened by extreme rhetoric (e.g., insinuations about Discord and “vibe coders”).
- Some acknowledge valid technical critiques but feel they’re buried under hyperbole and moralizing.