Idea looks really really nice.

Not sure how some edge cases (?) are handled. For example if a database server goes down, my app that uses pledge needs to open another socket to another server. Reload of changed configurations?

"Unpledge" then pledge again? Whitepaths?

I think being able to "unpledge" would defeat the purpose of pledge. Instead, I think the better way would be to have your app run by a parent, and when you lose connectivity to your db server, you crash your app on purpose and whenever your app crashes, parent restarts it. Problem solved, I think.

Thanks!

Content starts at around 14:30 minutes if you want to jump over the bashing of others and self-adulation by Theo.

But you miss the wonderfully absurd gif at the ~02:00 mark.

"She was 35, had been with the company for four years, and was told without explanation by her 28-year-old manager"

What's the fuzz about the ages? Age discrimination by NYT author?

"There is no mention at all of use of Mossack Fonseca by massive western corporations or western billionaires – the main customers."

Such as strong claim ('main customers') would be nice to be substantiated.

Also the author needs to show the data is there.

If this is the map (linked in another comment), and it main customers were not cut out, then it doesn't look as it has a lot of e.g. US content.

https://briankilmartin.cartodb.com/viz/54ddb5c0-f80e-11e5-9a...

The soccer star is from the Panama leaks.

If you quote these, then why not the more completly:

"CPI reports receiving foundation support from a number of foundations, including the Sunlight Foundation, the Ethics and Excellence in Journalism Foundation, the Ford Foundation, the John D. and Catherine T. MacArthur Foundation, the John S. and James L. Knight Foundation, the Omidyar Network, the Open Society Foundation, and the Pew Charitable Trusts.[31] The Barbra Streisand Foundation reports that it has funded CPI." -Wikipedia

And from their website: "Recent ICIJ funders include: Adessium Foundation, Open Society Foundations, The Sigrid Rausing Trust, the Fritt Ord Foundation, the Pulitzer Center on Crisis Reporting, The Ford Foundation, The David and Lucile Packard Foundation, Pew Charitable Trusts and Waterloo Foundation."

From the reporting:

- Fat Cat Hotel: How Democratic High-Rollers Are Rewarded with Overnight Stays at the White House.

- Windfalls of War, a report arguing that campaign contributions to George W. Bush affected the allocation of reconstruction contracts in Afghanistan and Iraq

- CPI's report, Who’s Behind the Financial Meltdown?,[45] looking at the roots of the global financial crisis

- Tobacco Underground, an ongoing project tracing the global trade in smuggled cigarettes

(All from Wikipedia)

It is funny how in your head, one image of a company is replace by another over time. It does not happen instantly, but with more and more actions by the company (open source .NET, Ubuntu on Windows,...) the image changes over time. I found that fascinating watching myself change the image of MS in my head.

"we've been on the receiving end of platform changes too many times to count."

But this is the value you provide, this is your raison d'etre.

So true. IFTTT is the glue not the paper. If they wish to go ahead and glue the papers accurately, it's not the paper producers job to make sticky paper.

This is a legal, future setting precedent for ifttt and they're gambling on weaker websites to get squeezed.

As always, if you're HNs darling, it's fine to send the lawyers.

As is sometimes the case, people start with the wrong abstraction (thread pool) and then optimize it.

Java/Scala streams look like they would solve most of the problems in the post on their own.

e.g. Java streams

http://radar.oreilly.com/2015/02/java-8-streams-api-and-para...

    private void runParallel() {
      trades
      .stream()
      .parallel().forEach(t->doSomething(t) );
    }

Java/Scala has a hierarchy of concurrency abstractions, from high level to low level:

Streams, Parallel collections, Futures, Actors, Fork/Join, ExecutionContext/ExecutorService, Threadpools, Threads, synchronized, Barriers, Atomic values and many more.

Something not so obvious for beginners: Java/Scala does not use all the available memory. If you get out of memory problems with the 10gb data set and you have much more RAM available, you need to tell Java/Scala to increase the Heap.