agilord

"Learning to write games on the side"

Randomizing children at hospitals would likely have big negative impact on society. On the long term, everyone would loose social cohesion because of the lack of bonds between brothers, nieces, whatever.

Families would lose every incentive to have a child in the first place, if it would be randomly switch to another (things like inheritance, family history and lineage comes in my mind). On the other hand, adoption would surely skyrocket.

Care to provide pointers on the correlations (research paper, whatever)?

Last time I've tried to install (~ 9-10 months ago): - Stash: it was a no-brainer (easy setup, easy use). - GitLab: hours spent with frustration (hard to setup, but this might have changed now, I need to try it again).

Stash seem to have a larger team behind it, with more features, documentation and snappier responses, but GitLab is promising too. I hope they all can be profitable and keep up the speed of improvements in all of the products.

If you publish something, it can be read everywhere. There should be no surprise that people will judge your words based on their customs, on their laws, on their terms, and they will act within their jurisdiction.

But that goes both ways: if a "Nigerian prince" scams you, you will not stop just because you were originally out of his jurisdiction.

I think Tim O'Reilly or Jeff Jarvis or Clay Shirky (unfortunately I don't have the bookmark anymore) already addressed this:

The case is a prime example that what you write is not only the jurisdiction where you write it, but also the jurisdiction where people read it. (And the jurisdiction where it stored and where it is going through as network traffic.)

Is there any benefit to use Presto on top of Riak or ElasticSearch (assuming someone writes the required connectors)? What are the main differences there?

You do realize, that because of the increase of content publishers, getting ranking becomes harder anyway (independent to Google).

I agree, banks and financial institutions are data driven businesses.

I have seen several banks from inside, and most of them think that they are driven by financial analysts, figuring out clever equations for managing money (e.g. lending rules, mortgage policies, etc), while IT is just a cost center for tracking the transactions. It's old school, and they change very slowly.

Sooner or later they shall realize that the transaction data they are tracking is a good source of information, and they could use "hard" data (through some machine learning and data mining), instead of or alongside of the "soft" intuition of their analysts.

I assume you have 'events' that you will 'merge' together in a single state object (in case you want to display something). So the operation is to fetch every related event, merge, display.

Now the 'folding' can be defined as snapshotting the 'merged state'. Instead of fetching 10 events, after the folding + GC, you will fetch e.g. 2 + the folded one. You are saving some CPU and bandwidth over time and that's it.