omphalos

There are a lot of ways that you can still be easily tracked in incognito mode such as browser fingerprints, supercookies, and WebRTC to name a few.

I wonder if web-of-trust SSL is the right way to solve this.

> Same as now.

Along similar lines, I think it's strange that I now see warnings in Chrome for SHA-1 certificates but no warnings at all for http.

You can do it now without a transpiler if you set harmony flags in Chrome/Node and use yield+co. (And just use a transpiler for deployment.)

One approach to countering sock-puppetry as a general problem is with increased transparency. Personally, I think lobste.rs' notion of a user tree is a step in the right direction: https://lobste.rs/u

There are a number of JS-in-JS stepping interpreters posted in this thread, one of which I've worked on :) For people who like this sort of thing, I think tailspin [1] is a particularly interesting example, since it supports reversible execution as well. [1] https://github.com/wthimbleby/tailspin

"No money ever changes hands with Humanity Box", but their partner, GiveForward, a for-profit company, seems to charge fees: http://www.giveforward.com/learn#fees.

GiveForward's remarks defending why they are for-profit: http://help.giveforward.com/customer/portal/articles/757696-...

And something like groupBy is even worse.

There is an interesting area of computer science called [inductive programming](http://en.wikipedia.org/wiki/Inductive_programming) dedicated to this sort of thing, though in a slightly different way than shown in this blog post.

One improvement that this has over most of the "conventional" reversible debuggers mentioned in the comments is the ability to instantly see the effect of your change over time. For example, with Mario example, after jumping up and down, you can adjust the gravity parameter to see what paths Mario would have taken with different gravities and the same input stream.

With that style of view, I suppose it's probably pretty easy to adapt Mithril to support server-side rendering.

Pretty interesting! I did something similar with UI code recently (https://github.com/omphalos/earhorn), although with the goal of runtime variable inspection instead of performance tracing. JavaScript makes instrumentation really easy and I kind of feel like the potential of this simple technology as dev tool hasn't been fully tapped.

Sadly I suppose this implies the impossibility of Malament-Hogarth hypercomputers.

You might be able to use dev tools to generate the curl request.

FWIW you can don't need VS for that - you can do this in Chrome by itself with the recent workspaces feature. Worth checking out.

Maybe there is one an I'm just missing it, but I'd love to see an OWIN-based benchmark in that list.

There's tamejs (https://github.com/maxtaco/tamejs)

One proposed alternative to await (for CoffeeScript) that is more one-to-one with the generated JavaScript: https://github.com/jashkenas/coffee-script/issues/2762

Median is more informative than the mean with this sort of thing