Skip to main content

Posts

Showing posts from August, 2019

Why Dropbox sunsetted its universal C++ mobile project and AirBnB its React Native implementation

Dropbox:  The (not so) hidden cost of sharing code between iOS and Android By writing code in a non-standard fashion, we took on overhead that we would have not had to worry about had we stayed with the widely used platform defaults. This overhead ended up being more expensive than just writing the code twice. The overhead of custom frameworks and libraries The overhead of a custom development environment The overhead of addressing differences between the platforms The overhead of training, hiring, and retaining developers Although writing code once sounds like a great bargain, the associated overhead made the cost of this approach outweigh the benefits (which turned out to be smaller than expected anyway) Dropbox Blog Airbnb: Sunsetting React Native [..] As a result, moving forward, we are sunsetting React Native at Airbnb and reinvesting all of our efforts back into native. React Native at Airbnb @Medium.com

Firebase realtime database stability - and monitoring

Firebase SLA Firebase will use commercially reasonable efforts to make Firebase available with a Monthly Uptime Percentage (defined below) of at least 99.95%, in each case during any monthly billing cycle (the "Service Commitment"). Firebase SLA Service Level Agreement for Hosting and Realtime Database Firebase Status Page Why Firebase sucks In the 3 years since starting to use Firebase we’ve suffered from so many outages I’ve literally lost count. @ Medium.com Status History Overview Statusgator Does anyone has real-life experience with the stability of Firebase or Firestore? Please leave a comment! We heared that Firestore is much more stable than Firebase which usage for new project is discouraged...