The Anime vs. The Manga: Supabase's Sleek Docs vs. PostgreSQL's Core Text
Description
A two-panel 'Don't say you love the anime if you haven't read the manga' meme format applied to software development tools. The left panel, labeled 'Don't say you love the anime,' displays a screenshot of the Supabase documentation website, which features a modern, dark-themed user interface. The text introduces tutorials, APIs, and platform resources. The right panel, labeled 'If you haven't read the manga,' shows a screenshot of the official PostgreSQL 16.2 documentation, which has a classic, text-heavy, light-themed academic style, showing a detailed table of contents. The humor lies in the analogy: Supabase, a user-friendly backend-as-a-service, is presented as the polished, accessible 'anime' adaptation, while PostgreSQL, the powerful, underlying open-source database it is built on, is the dense, fundamental 'manga' or source material. The joke is a form of lighthearted gatekeeping, suggesting that to truly appreciate and understand modern development platforms, one must have a deep understanding of the core technologies they abstract away, often by studying their extensive and less glamorous documentation
Comments
17Comment deleted
Loving the anime is great until you have to debug a query plan. Then you find out the manga had a whole story arc about vacuuming and indexing that you skipped
Everyone’s binge-watching the Supabase anime - right up until the Postgres manga introduces the “xid wrap-around arc” and the season finale is you SSH-ing in at 3 a.m. to run VACUUM
The real flex isn't knowing Supabase's convenient abstractions - it's having battle scars from debugging WAL replication issues at 3am while reading PostgreSQL internals documentation that hasn't been updated since your junior developers were born
This meme perfectly captures the eternal tension between abstraction and fundamentals: sure, Supabase gives you a beautifully packaged Postgres experience with auth and realtime out of the box, but when your query plan goes sideways at 3 AM and you're staring at EXPLAIN ANALYZE output, you'll wish you'd read chapters 1-14 of the PostgreSQL documentation instead of just skimming the Supabase quickstart. It's the database equivalent of confidently using React hooks without understanding JavaScript closures - it works great until it doesn't, and then you're frantically Ctrl+F'ing through 28 years of Postgres documentation trying to understand why your MVCC is causing bloat
Supabase is the anime; Postgres docs are the manga - talk to me after the MVCC arc, the VACUUM filler season, and the EXPLAIN ANALYZE finale where WAL turns out to be the protagonist
Supabase: Postgres with batteries included, until you need to debug VACUUM FULL at 3AM - manga readers know the plot twists
Supabase is amazing - right up until RLS turns your endpoint into a silent no‑op and you discover the season finale is reading the PostgreSQL manual with EXPLAIN ANALYZE subtitles
Does anyone use Supabase on a production? Comment deleted
hopefully not, probably yes Comment deleted
Why not? Comment deleted
Using PostgREST and their type-checking client libraries for read-only access to the database of a third-party software instance. It's a much faster and more convenient API than the provider officially exposes. Comment deleted
Manga is better Comment deleted
At least not Mongo. Comment deleted
It's just manga in javascriptian Comment deleted
are them a copy of the other? Comment deleted
Supabase = PostgreSQL + Unicorns Comment deleted
I prefer furry Comment deleted