4 ms·
The official Android testing framework from Google is also named Espresso. Are we running into a classic hard computer science problem?
by Apocryphon 10y ago
The official Android testing framework from Google is also named Espresso. Are we running into a classic hard computer science problem?
- Y_Y 10y agoOff-by-one errors?
- grkvlt 10y agoI'm sure he means something to do with caches; I had it on the tip of my tongue a moment ago, but the doorbell rang.
- spartanatreyu 10y agoHe means naming things
- andrewstuart2 10y agoSurely this is what he meant. Since edge peering/CDN is fundamentally caching (last I checked). It can't be off-by-one, and there are only 2 hard problems in CS, so there you have it.
- jenscow 10y agoI thought he meant IE support.
- bitwiseand 10y ago"There are only two hard problems in CS : 1. Naming things. 2. Cache invalidation. "
- coderholic 10y ago"There are only two hard problems in CS : 1. Naming things. 2. Cache invalidation. 3. Off-by-one errors"
- xapata 10y agoOnly you got the order wrong. One of those distributed systems problems.
- bitwiseand 10y ago"There are only two hard problems in CS : 1. Naming things. 2. Cache invalidation. "
- jamescostian 10y agoI'm pretty sure a lack of coffee is the real issue at hand. Google made more architecture to give peers an edge via two different Espresso shots to test
- IncRnd 10y agoNot if they developed using Espresso CSS editor that just had v3 released on March 30th.
- knorker 10y agoThere are two whole things at Google called "Espresso"? Oh no. I bet this reuse of a name has gone unnoticed internally until now.
- _pmf_ 10y ago> The official Android testing framework from Google is also named Espresso. This just shows that Android is treated as the ugly step child even within Google (not that this is not already obvious given the state of the Android API).