Get ready for @remmies's expert insights on #Android at #dcldn25 🇬🇧
Unpack #CoroutineContext beyond threading—see how it shapes #coroutine behaviour & simplify dispatcher use in projects. https://t.co/IRnBSiTCP1
@SanderSchimmelp@AntoonKanis Als dat het punt is, slaat het nergens op om de relatieve verandering te laten zien. Dat is dan toevallig een grafiekje waar Nederland onderaan staat maar zegt niks over de relatie tussen output per uur en aantal gewerkte uren.
@krossovochkin@n_haarman @lime_cl You'd write the fake for the analytics interface once and all feature that have analytics use the same fake. The fake exposes either a list of events the it recorded, or a method to assert that certain events were recorded.
@googlemaps I've been trying to update the correct construction situation near my house for months now and every time it goes wrong. All delivery companies l and guests get lost consistently and with every "fix" the routing only gets worse.
Then I suggested an edit that the middle part of the road is open, and accessible from another road. That edit also got published now, but rather than the middle, it now shows one of the parts that's actually closed as open.
@danielverlaan De fake security met fingerprint op Mac was ook al een hint wat LastPass beveiliging betreft. Als je MacBook open is moet je je vingerafdruk gebruiken om je vault te unlocken. Als je de MacBook op een extern scherm aansluit en MacBook dicht klapt geen authenticatie nodig. 🤔
@ZacSweers For some reason our incremental compilation benchmark sees a performance decrease when enabling this. A non-abi breaking change in core module sees a slight perf boost when bumping from 1.6.20 to 1.7.10, but then a perf decrease (worst than base) when enabling the flag.
@manuelvicnt To me it feels like preventing one-off things to happen multiple times is the problem to solve here. Isn't it a bit odd that that is solved in the example by calling activity.finish() since that's the easy way out?