Supabase-JS v2
31–40 of 82 posts
Re: Supabase-JS v2
#32It's a second release candidate, there are instructions for how to install it, apparently it's really popular (congratulations btw :)), but there's no mention of its actual purpose. Could be another JS engine, a new Postgres JS extension, or who knows what else.
Wouldn't have hurt to get the GitHub repo description "An isomorphic Javascript client for Supabase." in there somewhere!
Re: Supabase-JS v2
#33It's wild that their whole value proposition seems to be "It's a Firebase clone, but open source."
Re: Supabase-JS v2
#34I cannot recommend their platform enough to anyone who hasn't tried it yet! It's going to be my platform of choice for all my upcoming projects. Keep it up!
Re: Supabase-JS v2
#35I love the concept of Supabase. The Firebase model is powerful but gated. For example, I recently had a project exceed FB's quota of functions- you can't deploy more than 60 endpoints in a minute which is a nightmare for CI pipelines which redeploy the entire app [0]. We recently tried Supabase on a "frontier" project, and found that it wasn't quite mature enough for production use in our case. Intermittent network e…
Re: Supabase-JS v2
#36Supabase user here. Ive been happy with Supabase. It feels like the recent launches have been underwhelming. I am really pumped for Neon and think they are doing something more differentiated.
I'm curious, care to drop a link about this Neon you're referring to? Thanks!
Re: Supabase-JS v2
#37Supabase user here. Ive been happy with Supabase. It feels like the recent launches have been underwhelming. I am really pumped for Neon and think they are doing something more differentiated.
if you like Neon, then I imagine you like their database branching model? On Friday we announced[0] our 500K investment into OrioleDB, who are working on branching[1], with the plan to upstream these changes into Postgres core.
It would be possible for us to run a fork of Postgres today which supports branching, but our long-term view is that developers would prefer a non-forked version of Postgres (to mitigate any risk of lock-in). So we will work on adding branching to Postgres core in the background, which will be a benefit to the entire Postgres ecosystem.
[0] Announcement:https://supabase.com/blog/supabase-series-b#where-were-going
[1] https://github.com/orioledb/orioledb/wiki/Database-branching
Re: Supabase-JS v2
#38congrats team! i like how you used detail/summary tags to truncate the v1 vs v2 diffs. > It is a bit surprising that you need to add a select policy to do an insert, so we opted for the “principle of least surprise”. If you don't append select(), the data value will be an empty object: {}. i wonder if there will be dev-mode assistance/hints for people who may be surprised by this. I'm very excited for the multiplayer…
We mostly rely on Postgres' errors to bubble up through the client libs which, coincidentally, is one of the things we've improved in this release. Most of the servers now are passing the Postgres errors through, and we're standardizing on the Postgres error format.
There's a lot more we can be doing here, but it's a step in the right direction
Re: Supabase-JS v2
#39Maybe it's been discussed before but since it's a VC backed company, what's their business model? They raised a ton of money. How do they plan on getting that back?
Re: Supabase-JS v2
#40I love supabase and im using it on one of my projects. The only downside is the storage abstraction on top of S3, those Egress fees are huge. I would love to see a Backblaze b2 integration.
I assume for the File Storage? We've designed this server for additional storage providers, and since Backblaze is s3-compatible it shouldn't be too hard to add. Would love a PR if you're up for a challenge!