Facebook should run an ad on the front page of NYT (and similar outlets elsewhere) showing a screenshot full of the 1-star reviews and the caption: "we will not bend to terrorism".

The right kind of donation will result in all charges dropped, nothing to be pardoned for.

The main problem was that they did not build a clean seam between C++ and platform-specific layers, but decided to use djinni that would automagically connect the two worlds.

We tried djinni in a smaller project, and our team faced many problems with this framework – not because it did not deliver on its promises, but because it turned our execution flow into a callback chaos, and debugging into nightmare.

Eyal writes about the same experiences, but attributes them to the hybrid C++/(Java and Obj-C) nature of the project. I have not seen same kind of troubles in other hybrid projects. IMO, it's djinni which discourages discipline in defining clean C++ API for the cross-platform core.

Quite a few contemporary solutions (e.g. http://www.mini-frame.com/) rely on sharing single CPU resources between a group of users. Their major price advantage was a single Windows/Office license. The new scheme will dirve these guys out of business.