On: Reasons not to use Firebase

[pavlov]

This kind of reminds me of those "we used MongoDB to build our social network and it sucks" articles from a couple of years ago.

[jsmith0295 → pavlov]

I'm amazed at how many people have that attitude about things they just didn't know how to use

[nevi-me → jsmith0295]

It eventually becomes a reputation and perception problem. For example, I've been happily using MongoDB for years now. The problems I've had with it are either:

1. Problems that I can solve by doing enough research up-front (how to model my data, enforcing constraints on my collections, testing something on small datasets first). 2. Problems I would have had on other systems (crashes where I didn't backup data, slow queries, etc.)

I love PostgreSQL, and I keep getting amazed by it as I dig deeper into it. I've however chosen to rather learn, and not have unhealthy biases towards and against certain tools and technologies.

I could say the same about the effort I put into most other tools that I rely on.

[akerro → jsmith0295]

That's one of the best reasons not to use people in your next project.

[jsmith0295 → akerro]

Man that sounds perfect :)

[baptistejamin → jsmith0295]

I worked with several Firebase apps, worked with Firebase protocol to make my own server. It's why we started with Firebase.

I really understand how to use it, how it's works (including server side, internal protocol).

Many people here talk about our example about relationships and we wanted to explain it to beginners, with a simple relation.

In our case, we had many relations, many data.

[vacri → jsmith0295]

People have to learn sometime. Not everyone is a grizzled old veteran.

[jsmith0295 → vacri]

In my experience senior people tend to do this as much if not more than everyone else, though.