No post body was provided.
Supabase-JS v2
11–20 of 82 posts
Re: Supabase-JS v2
#12Much prefer the DX of the types inferring from the `from` and `select`. Also really love that `insert` now understands if a field is required (or has a server-side default etc.)
Unless I am missing something we seem to have lost all typing for Views? And it is less clear how to use PostREST style embedding?
Re: Supabase-JS v2
#13Maybe 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?
their whole thing seems to be to capitalize on rightful faang skepticism to become the default paas over firebase. the model is same as any other paas. going off my network it appears to be working, but making the whole sell "we're open source" makes me wonder if it'll still be a leader in 5-10 years
Re: Supabase-JS v2
#14I 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…
Why not have a single function that uses a router? Just map /* to the function and within the function, make your calls to other discrete handlers.
Re: Supabase-JS v2
#15Maybe 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?
its brought up every time supa is on hn. reasonable qtn but here you go https://news.ycombinator.com/item?id=32440018
Re: Supabase-JS v2
#16I 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.
Re: Supabase-JS v2
#17I 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…
Why not have a single function that uses a router? Just map /* to the function and within the function, make your calls to other discrete handlers.
That is the exact solution we went with :)
Re: Supabase-JS v2
#18Maybe 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?
its brought up every time supa is on hn. reasonable qtn but here you go https://news.ycombinator.com/item?id=32440018
Your answer didn't answer anything and was a bit terse. Their question was valid.
It looks like the answer is that they're charging some sort of licensing fee per project using Supabase or that they have a hosted option for people who don't want to run their own Supabase instance(s): https://supabase.com/pricing.
Re: Supabase-JS v2
#19Earlier quoted context omitted.
Why not have a single function that uses a router? Just map /* to the function and within the function, make your calls to other discrete handlers.
That is the exact solution we went with :)
So then why mention that FB is gated? It isn't gated, the design of your application was off.