can there just ONCE be a FUCKING react native library that works as it is FUCKING documented?

but NOOOO, gotta always sift through the absolute shit pile that is GitHub issues threads digging out arcane horseshit to make the stupid shit work just like the little managers want

on and on into the circus enternity

Which library are you facing issues with?

From my experience usually they work as intended BUT majority require extra effort if you want to customize within the supported features of the library itself.

Recently we've hit a bug in React Query that can only be solved by upgrading to v4, we are using v3 now, and the migration guide caused us pain and heart attack because of the amount of work required to migrate :\

@gitpush Two words: google maps

@fullstackclown I take back what I said it's good for map display but good luck using the restof the features I recall it gave me lots of issues a year ago not sure about the status now but you summarized it lol

When da internal money making stuff is thrown out for external use it's usually bad.

Note that this is not specific to Google.

I've seen a lot of APIs and especially Amazon, eBay and PayPal come to my mind in addition to Google...

Gmaps is bloated by closure library.

React is also bloated, by facebook.

Why not build the app in HTML5/CSS3/vanillaJS?

@max19931 ah yes, because every single one of us on this site works on the web.

how could I forget? so stupid of me!

🤡