emil10001

From the article:

"Apple had asked the F.B.I. to issue its application for the tool under seal. But the government made it public, prompting Mr. Cook to go into bunker mode to draft a response, according to people privy to the discussions, who spoke on condition of anonymity. The result was the letter that Mr. Cook signed on Tuesday, where he argued that it set a “dangerous precedent” for a company to be forced to build tools for the government that weaken security."

I would qualify, I've done both servers and Android at Talkray. It's been a while since I have done both in the same day, but basically, if something broke on our Android client or server, I could jump in and get a fix, same goes for new features, and handle the server deployments.

That said, I'm happy that I don't have to do both. Oh, and right now, nobody's going to poach me. =)

That's interesting, I had not come across CompletableFuture yet, I'll need to dig in more, but the JavaDoc looks promising (if confusing). It sounds like RxJava may also handle the backpressure issue, where you provide threadpools for the execution and handling of an observable.

I haven't played with Guava, but I have used Otto a bit, and at one point wrote my own simple observer framework (which is slightly less work than implementing a Java Observer). As I wrote in the disclaimer, there are lots of ways of doing this. =)

I remember visiting the #coffee IRC channel years ago, and really enjoying being able to converse with people real-time on roasting, espresso, and everything coffee (or off-topic stuff). While the IRC channel still exists, I sort of figured that a Slack community for coffee was inevitable, and was a bit surprised that there wasn't one already. Anyways, I hope that some of you will come join me there.

Reads more like satire to me.

Slimming down Play Services just punts on the problem for a while. My view is that Google needs to do two things with this:

1) Split up the Play Services client libraries. 2) Figure out some solution for developers hitting the 65K limit.

I'm sort of assuming that the solution would come in the form of a framework or tooling that we'd have to implement. Such a solution should allow us to build fully working apps with multiple dex files, with some decent documentation. It should also work fine for debug builds without proguard, and also without bumping build times up beyond a two minutes. What's more, we should be able to split off pieces that are defined in the manifest into secondary dex files, and fire intents at them.

That, to me, seems like a reasonable response to this problem by Google. The company I work for has been hitting the limit for the last few months, and some of our other dependencies are becoming more and more expensive with newer releases (things that our users actually like.) So far, we've been able to build with a stripped down Play Services jar, but I'm not terribly happy about that approach.

Regardless, I'm not going to blame Facebook for a problem that Google caused. If Facebook can find a solution, and tell the community how they did it, I'm all ears.