Open sourcing the Firebase SDKs
opensource.googleblog.com
Open sourcing the Firebase SDKs
1–10 of 77 posts
Re: Open sourcing the Firebase SDKs
#2I was an early Parse engineer (4th engineer to join the company) and now am the SDK engineering lead for Firebase.
The experience of working on Firebase at Google is vastly different from Parse at Facebook, and it shows in Google’s continued commitment to building and expanding Firebase, integrating it with its Cloud Platform products, and otherwise pouring huge amounts of effort into making Firebase great for developers. Open sourcing our SDKs gives us even more ways to engage with the developer community and allows us to be more transparent with the progress we’re making.
This announcement is just a first step down the path toward more transparency with our SDKs, but we hope to foster community and build trust in the tools we’re developing, and welcome your contributions!
Re: Open sourcing the Firebase SDKs
#3what's new? Bug fix that increases costs by a huge amount. It's a feature not a bug ;-)
Re: Open sourcing the Firebase SDKs
#4I was an early Parse engineer (4th engineer to join the company) and now am the SDK engineering lead for Firebase. The experience of working on Firebase at Google is vastly different from Parse at Facebook, and it shows in Google’s continued commitment to building and expanding Firebase, integrating it with its Cloud Platform products, and otherwise pouring huge amounts of effort into making Firebase great for develo…
That's great! But it does make sense why google and FB would be taking different paths here.
As much as I was disappointed with FB's decision on Parse, I can also understand the reasoning behind it and I actually think it was the right decisions for the company. In contrast, Google is playing in the cloud service vertical and investing in the future of Firebase is totally aligned with that objective.
Re: Open sourcing the Firebase SDKs
#5How about open sourcing the realtime database server?
Would love to be able to do offline local development.
Re: Open sourcing the Firebase SDKs
#6what's new? Bug fix that increases costs by a huge amount. It's a feature not a bug ;-)
There have been some updates on this situation for those that caught it earlier today.
Original post has been updated about being contacted by Firebase: https://medium.com/@contact_16315/firebase-costs-increased-b...
Firebase founder comment on Medium about it: https://medium.com/@startupandrew/firebase-founder-here-im-v... (and he posted the same thing on the HN thread https://news.ycombinator.com/item?id=14359801 )
(I work at G, opinions are my own).
Re: Open sourcing the Firebase SDKs
#7I didn't even know that the client was not open source.
What makes this Firebase less risky than Parse or the recently deprecated Prediction API?
Re: Open sourcing the Firebase SDKs
#8[deleted]
Re: Open sourcing the Firebase SDKs
#9Not any news on the Fabric dismantle. What brand stays alive? Will everything become Firebase?
Re: Open sourcing the Firebase SDKs
#10[other Firebase founder] It was painful to read the article[1] this morning, especially since I was one of the people responsible for dropping the ball on getting Home Automation the credit to cover the overage a few weeks ago. We're working with the founder to make sure he's in a better spot. If you have similarly serious issues, my email is: james@firebase.com
To address a couple of points that have been raised:
1. We're aware that as we've integrated with Google our support response time & quality has decreased. I'm working with our team to do better.
2. We know better querying and web offline are needed for the Realtime Database, stay tuned.
Finally, I hope you enjoy all the new features that launched today! (https://firebase.googleblog.com/2017/05/whats-new-from-fireb...) Leave a comment if you have thoughts/comments.