davideast

8 ms·

1.
Delivering Messages at the Scale of the World Cup(firebase.blog)
6 points by davideast 3y ago|0 comments
2.
Sampling Bias, FDR, and the State of JavaScript(davidea.st)
1 points by davideast 7y ago|0 comments
3.
by davideast 8y ago
That is not true. The default access is only to authenticated users.
4.
by davideast 8y ago
No it does not. By default it locks down your empty database to only authenticated users.
5.
by davideast 9y ago
Yep, more wording was bad. In HTTP/2 it's all parallel.
6.
by davideast 9y ago
Sorry, wrote this before coffee. I was referring to H/2 eliminating head-of-line blocking. HTTP/2 gives you one TCP connection for multiple requests rather than the 7 connection limit browsers impose on HTTP 1.x
7.
by davideast 9y ago
HTTP/2 happened. HTTP/2 allows you to send HTTP requests over a single TCP connection per domain. Headers are compressed. The request overhead is minimal compared to HTTP/1.x. Caching one big file has the draw back of busting
8.
by davideast 9y ago
I highly recommend using Workbox: https://workboxjs.org/ . One of the more gnarly parts of ServiceWorker is having to clean up old caches during a version change. The workbox-build module generates revision hashes for your p
9.
by davideast 10y ago
Hello, Firebase YouTuber, Slacker, AngularFire contributor, and Stackoverflower here. Feel free to ping me personally in the Slack channel (davideast) of via email (david@firebase.com) to talk more about all of these problems you've hi
10.
Progressive Web Apps: A Chrome Dev Summit Recap(medium.com)
1 points by davideast 11y ago|0 comments
11.
by davideast 12y ago
[Firebase Employee] If you use the SDKs, we handle the connection and all of the data is sent over a reused full duplex socket rather than individual requests. https://www.firebase.com/docs/android/ , https:/