We’ve been developing this product for quite some time, and we’ve had it in private alpha testing for well over a year. We’re incredibly excited to finally take the wrappings off and let all of you try it.
Firebase has always focused on empowering you all to build extraordinary experiences for your users, without needing to worry about building common infrastructure. While we’ve made big strides towards this vision in the past, we always had one big hole: trusted code execution. Today, we’re completing the story with Cloud Functions for Firebase so that you can easily run server-side code in response to events from your Firebase app.
We think you’re going to love it, and we can’t wait to see what you build with it!
We’ve been developing this product for years, and we’ve had it in private alpha testing for well over a year, so we’re incredibly excited to finally take the wrappings off and let all of you try it.
Firebase has always focused on empowering you all to build extraordinary experiences for your users, without needing to worry about building common infrastructure. While we’ve made big strides towards this vision in the past, we always had one big hole: trusted code execution. Today, we’re completing the story with Cloud Functions for Firebase so that you can easily run server-side code in response to events from your Firebase app.
We think you’re going to love it, and we can’t wait to see what you build with it!
Brendan, this is exciting news for lots of people! I'm developing a product on Firebase now and trusted code execution has always been my biggest concern.
Sure, it could be mitigated, but all the workarounds added unnecessary overhead and breaking points.
Want to thank you and your team for working on this. Firebase is a great product and this will make it just fantastic.
One thing if I have your ear - I'd love to give Firebase team some money by purchasing paid support - ideally as a part of the new Google Cloud support options announced yesterday. I hope this is on your roadmap as well :-)
From an onboarding and testing perspective, it would be nice to be able to integrate other services ("Outbound networking"?) in the free tier. Maybe limit to one connection?
There's a bit of a nuance here. Even if you join the Blaze plan (pay as you go) there's still a large free quota. The quota is actually much larger than you get with Spark as well. We just can't allow arbitrary REST calls without a credit card. This helps avoid Cloud Functions being used for abuse/malware.
Cloud Functions for Firebase tech lead here. We'll get there in the future. We're looking forward to getting more feedback from users & prioritizing what is next.
No. All events are asynchronous. This use case is best simulated by having clients post to a queue. Cloud functions then either discards or applies writes in that queue.
You should add this technique to the docs! It makes you realize that the Cloud Functions feature is a lot more powerful than you might initially think.
The world needs more people like Garry Tan. He's one of the kindest, humble, and most genuine people you'll ever meet. Garry helped us tremendously during and after YC.
Can't wait to hear to see what you end up doing next! Thank you, Garry!
Nice job creating your own implementation of UITableView. Although, if you find delegates and datasources unusual then its best for you to spend more time getting familiar with them rather than trying to work around them.
That said, I tried to write the post to be geared towards the beginner audience. And I remember when I first started iOS development, UITableView seemed weird.
It comes with two delegate objects with separate responsibilities (delegate and dataSource) and is pretty ubiquitous, so you may interact with it right away when first starting iOS development, before interacting with the many other classes that use delegates (and the, what, 3 others that use dataSources).
To a beginner, that tends to make UITableView stand out as an unusual thing.
I'm hoping pulling UITableView apart, and explaining the machinery can help make those design decisions more clear.
I have not read your post in-depth, I will, but I think it's probably wise to stick to learning UITableView well -- and understanding why I would want to implement something custom -- before avoiding the classes Apple provides.
That being said, I understood delegates, categories, and other Objective-C features much better after coding several applications first, reading a ton of open source code, and then reading relevant parts of Programming in Objective-C (Kochan). I first purchased his book before attempting to code for iOS, and found the pace too slow or concepts too unfamiliar, but after some practice and finding what I did not understand, it is much easier to look to documentation and textbooks for appropriate reference.
Here's to demystifying the internals of UITableView! Your tone seemed fine to me. Glad you geared it towards newer folks to iOS. I remember when I was first starting with iOS, one of the biggest questions I had on these things was "Why?". Luckily posts like this, and the treasure trove of Mike Ash's blog provide a clear understanding of both how the components in Cocoa work, and why they work that way.
Kicksend was part of the YCS2011 class. We raised a $1.8 million seed round from some amazing investors. At Kicksend (http://kicksend.com) we're making the act of sharing and receiving files extremely simple and effortless.
We're looking for:
★ Android Developer
★ iOS Developer
★ Windows Developer
We pay very well, have stellar benefits, emphasize a sane work-life balance as much as possible and offer an equity stake. We’re based out of beautiful Mountain View, a prime startup hub in Silicon Valley.
That is definitely not our intention. We added the automatic screenshot uploading because we thought it'd be useful for us. It's something we use everyday and we thought others would like it as well. We will be releasing a new build today that turns this off by default.
We’ve been developing this product for quite some time, and we’ve had it in private alpha testing for well over a year. We’re incredibly excited to finally take the wrappings off and let all of you try it.
Firebase has always focused on empowering you all to build extraordinary experiences for your users, without needing to worry about building common infrastructure. While we’ve made big strides towards this vision in the past, we always had one big hole: trusted code execution. Today, we’re completing the story with Cloud Functions for Firebase so that you can easily run server-side code in response to events from your Firebase app.
We think you’re going to love it, and we can’t wait to see what you build with it!
Non-Firebase related Cloud Functions discussion is here: https://news.ycombinator.com/item?id=13831398