#1 Taking off with Supabase

I have promised it long time, now I will deliver. You will get regular Supabase Snack newsletters from me, to pump up.

What’s a Snack newsletter? I’m trying to be different.

You get enough shit in your mailbox. I’ll send you essential, digestible, potentially interactive snack pieces.

Hit me up

You can respond to this newsletter. I’ll try to respond as much as the volume allows me.

Spot the bug

await supabase.from('supa_guide')
  .select('email_title, email_content')
  .order('id', { descending: true })
  .limit(1)

Snack 1/3: Supabase is vendor-lock in?

In a surprising tweet, a recent poll by Supabase’s frontend dude Jordi revealed that 48 of 152 respondents believe Supabase is just as much a vendor lock-in as closed platforms like Firebase.

This result is unexpected—especially considering that Supabase even acquired Logflare, committed to reworking the code, and made it fully open-source.

• https://supabase.com/blog/supabase-acquires-logflare#open-source

• https://github.com/Logflare/logflare/blob/main/LICENSE.md 

What do you think is the reason?

Snack 2/3: 2 Supabase projects aren’t 50 USD

In a Pro plan, you pay 25$ USD, no matter if you use it or not.

Then, on top of that, there’d come ~10USD for the Micro instance per month, so why isn’t it 35$?

That’s because you get 10$ of free credits every month: 25$ + 10$ - 10$Free = 25$.

Every additional Micro instance then is again 10$. That means: 2 small Supabase projects are ~35$, 3 are ~45$, etc. Get it? Here’s my bill from last month:

Snack 3/3: How can I get what I have on my remote instance into my local instance?

How about 2 commands and you’re done? If you have worked on the remote so far and only wanna have those changes locally, it’s really frickin’ easy. Here’s the video I did.

I quote the guy in the comments