Re:Migrating from Supabase
by kiwicopple on Friday May 19, 2023 @05:45PM
(#36007204)
(supabase ceo)
> "I know feature X exists in postgres, but it's 'coming soon' in Supabase."
There is no feature that exists in postgres that doesn't already exist in Supabase. In case it's not clear, supabase is just Postgres. We build extensions, we host it for you, and we build tooling around the database. Our Dashboard is one of those tools, but there is always an escape hatch - you can use it like any other postgres database, with all the existing tooling you're most comfortable with.
Thanks for the response. I do recall hitting some product limitations (a webhooks "beta" that we tried to use but hit a blocker). Reflecting more, I don't recall the supporting details specifically enough though. Edited original post and apologies for the added noise.
I also had a tough time working w/ an app someone else built on Supabase. We kept bumping up against "I know feature X exists in postgres, but it's 'coming soon' in Supabase." Felt like they were just wrapping UIs around things that already existed via CLI/API. IIRC specifically some event trigger/webhook behavior was a blocker.
Candidly, some of these dev tool products that wrap a UI around existing technical solutions feel like obfuscation instead of abstraction [0]. Many mature tools such as postgres have honed their interfaces over time in response to real world use. The fact they are complex is the result of providing a solution to a hard problem ("complex solutions are always required for hard problems"). The solution is to do the work and learn how to use them well (or hire someone to do this), not create or learn to use an obfuscating intermediate layer.
To be clear - not saying we don't need more and better dev tools. We do, just perhaps solving for slightly different pain points.
[0] https://rule11.tech/obfuscating-complexity-considered-harmfu...
(Edited to improve brevity & tone)