4 ms·
I'd consider myself fortunate if I never have to deal with Firebase again. Firebase simply did not behave as documented. Whole features shipped that were just
by rectang 5y ago
I'd consider myself fortunate if I never have to deal with Firebase again.
Firebase simply did not behave as documented. Whole features shipped that were just wishful thinking.
It reeked of high-level management applying pressure to ship-now-no-matter-how-broken.
- vincentge 5y agoFirebase is great for Hackathons =D
- wfme 5y agoMy experience is quite different to this. I’d be interested to know which features behaved differently to their documentation?
- rectang 5y agoI most vividly recall unit testing, storage emulator, auth. For example: https://github.com/firebase/firebase-js-sdk/issues/5086 https://github.com/firebase/firebase-js-sdk/issues/5086 > Steps to reproduce: > Step 1: Read the documentation for setting up cloud storage unit tests at: https://firebase.google.com/docs/rules/unit-tests#storage https://firebase.google.com/docs/rules/unit-tests#storage > Step 2: Attempt to write unit tests following the examples in the documentation The reporter describes five problems which will thwart you when you try to write code according to the official documentation. How did these docs ship? Did nobody ever try the sample code and verify that the features worked as advertised? Did nobody write any tests to validate that the features actually worked? Are there no policies in place (e.g. "new features require tests" or perhaps code review) to prevent such mishaps?