Vibechart

Original Article ↗ Hacker News Discussion ↗

Chart errors and perceived deception

  • Discussion centers on OpenAI’s GPT‑5 launch charts, where bar heights don’t match labeled percentages (e.g., 50% vs 47.4%, 69.1% vs 30.8%).
  • Some see this as standard marketing exaggeration (like GPU/CPU launch graphs); others call it outright dishonest.
  • A few argue it’s likely a rushed human editing mistake or placeholder graphics left in by accident, but many say that’s still inexcusable at this level.
  • Later, more plausible versions of similar charts appeared in the official post, reinforcing the “sloppiness, not conspiracy” camp.

AI involvement and self‑referential irony

  • Several people joke/speculate that the slides were AI‑generated or edited (“using their own dog food”), noting that LLMs can miss obvious visual inconsistencies.
  • Others test image input on GPT‑5, finding it can detect the error if explicitly asked to look for mistakes, but not always unprompted.
  • The deceptive “coding deception” chart is mocked as a model “trying to deceive people about its deceptiveness.”

Marketing, vibes, and post‑truth themes

  • Many see this as emblematic of a “vibe world” / “post‑truth era” where perception and hype matter more than accuracy.
  • Some argue investors and the public largely don’t care about fudged numbers if the story is good and “stonks go up.”
  • The term “vibechart” is embraced as a label for charts optimized for vibes over truth.

Reactions to GPT‑5 and OpenAI’s competence

  • A number of commenters describe GPT‑5 as underwhelming or only an incremental upgrade, especially compared to competitors.
  • Others say the models are solid API improvements and will feel significant to non‑technical users.
  • The chart fiasco fuels doubts about OpenAI’s rigor; some worry LLM culture is normalizing sloppiness and indifference to correctness.

Site implementation and dev culture

  • The Vibechart site itself is critiqued for performance issues, iOS scrolling bugs, and heavy animations—used as an example of devs building on high‑end machines without testing on low‑end hardware.