Why is Firebase considered bad by most people? I'm currently in my "Firebase" phase (great for beginners) and it seems scalable, though the cost per read/writes makes me pretty paranoid about each of my calls. Any help to understand the main reasons why people are moving away would help me a lot! Thanks!
There are a lot to say here but the most common reasons are: the pricing model as you said and its consequences, like you need to duplicate a lot of data to work around pricing and probably the most important reason is that people expect it to work as relational database and it's not, so they either misuse it and get a big bill or complain about it and it's the worng choice for their use case in the first place. It's a fairly good baas, but has its niche.
also, people might have started to realize that vendor lock-in is not that great of a thing (obviously this needs to be discussed case by case, but still...)
Firebase is a pretty solid product. You have discord, whatsapp and other big products built on top of it, so scale is not a problem. I like supabase as well but they are different. Even if you use supabase you might want firebase crashlitics or realtime notifications, etc. firebase has a lot to it that supabase doesn’t. Also their tier pricing is pretty generous, you would have the same “issue” hosting supabase. And yes, in document dbs you duplicate data and that’s ok. All of this to encourage you. Most of the times is tech hype that can be a real slow down (it happened to me)!
For me.... Firebase docs is not that sweet and easy to use compared to Supabase ....... That's my only reason.... In firebase each version has very much different API that the previous but Supabase is unique with a larger community 😂😂
Supabase was my production even before all of these changes!
Yea it was kinda funny that they said it is now in GA, its great to here but lets be honest, I was gonna ship it regardless
Why is Firebase considered bad by most people? I'm currently in my "Firebase" phase (great for beginners) and it seems scalable, though the cost per read/writes makes me pretty paranoid about each of my calls. Any help to understand the main reasons why people are moving away would help me a lot! Thanks!
There are a lot to say here but the most common reasons are: the pricing model as you said and its consequences, like you need to duplicate a lot of data to work around pricing and probably the most important reason is that people expect it to work as relational database and it's not, so they either misuse it and get a big bill or complain about it and it's the worng choice for their use case in the first place. It's a fairly good baas, but has its niche.
also, people might have started to realize that vendor lock-in is not that great of a thing (obviously this needs to be discussed case by case, but still...)
Firebase is a pretty solid product. You have discord, whatsapp and other big products built on top of it, so scale is not a problem. I like supabase as well but they are different. Even if you use supabase you might want firebase crashlitics or realtime notifications, etc. firebase has a lot to it that supabase doesn’t. Also their tier pricing is pretty generous, you would have the same “issue” hosting supabase. And yes, in document dbs you duplicate data and that’s ok. All of this to encourage you. Most of the times is tech hype that can be a real slow down (it happened to me)!
For me.... Firebase docs is not that sweet and easy to use compared to Supabase ....... That's my only reason.... In firebase each version has very much different API that the previous but Supabase is unique with a larger community 😂😂
Postgres extensions like postgis
what app were you using at 4:25, the blog list
Arc Browser?
@@bmdavis419 the blog list view, is that how arc display bookmark or is it a supabase site that displays the blog vertically