13

Firebase is pure fucking assrape!
How can these spoiled cunts of Google "develop" such a stinking pile of rotten placenta?
No, one fucking Promise is not enough... you have to return Promises for every single smegma function!
I want to just blow up this ugly afterbirth!!

It seems that Google devs are just spoiled MacCunt Pro brats who copy-paste code around until something "kind of works".

Comments
  • 3
    I use async await plus try catch with Firebase, Firestore too.
    Not a single Promise.
  • 0
    I just use promises with the cloud functions bcz they doesn’t support async await... that’s a shame.
  • 3
    I'm a simple man. I see a rant against Google's pinnacles of Certified Enganeers, I ++ 😊
  • 1
    @Maartz Good for you.
    We use Firefuck Cuntions and there have to be at least 4 Promises to get the job done.
  • 1
  • 1
    Was never a fan of Firebase, I only use it for two things push notifications and analytics other than that I don't give a shit, I do my own API and store my data where I want.

    Luckily at work they have the same mentality and we never came across a project that forces us to use other Firebase features
  • 1
    @Condor Enganeers?
  • 4
    @Cyanide it's an AvE reference 🙂
  • 1
  • 4
    @Cyanide amazing YouTube channel, highly recommended!
  • 1
    Since nlde is evenr based, I though returning promisses every-fucking-where is a design pattern.
  • 1
    What's so bad about promises? Now I think I've got the hang of them, it beats the pyramid of callback hell.
  • 0
    @d4ng3r0u5 It is bad, when you, for example, get some user session data from a promise, but in order to get the user's id token of this session, you have to call a second promise.

    It's just fucking brainless to not return the relevant data all at once.

    This is just one example of many problems.
Add Comment