I contribute to https://www.coolearth.org/ which seems to be one of the best options following this approach

This is a really great tool. If it could take the first .csearchindex going up the tree as the current index (somewhat like git does with .git dirs), it could easily top rgrep/ack for searching into projects. (just add line numbers and some match coloring)

I found all of them very easy except "question 6", at which I'm still failing hard to visualize the difference, and is the only one I got wrong. (I had to choose a random one)

Well, I can tell you that eating beans (pretty much required for a vegan?) and cabbage hurts like hell. In fact anything that is a little too gassy. Eating a lot less tomatoes helps too. Milk is annoying, but not cheese, and especially not yogurt. I think yogurt actually helps you. I have no problem with meat, except when it's too bloody.

    ~ # cat over.c
    main () {
            int i = 0x00ffffff;
            while (i > 0) i--;
    }
    ~ # tcc over.c -o out
    ~ # time ./out
    real    0m 13.58s
    user    0m 13.57s
    sys     0m 0.01s

I love this stuff.

M-x ansi-term does colors, too

He should do a reddit AMA

My experience with siege is that it actually measures siege's terrible performance.

jpegoptim --strip-all, also optimizes for size without degrading quality.

Now, maybe I'm to blame here, using the nightly build of chromium, but webkit is a walking memory leak. Just for a comparison, I have the same amount of tabs on firefox and chromium and firefox is using 500mb of ram, while chromium is using 3.5 GIGABYTES. And I'm not even using it much. But really, the problem is easily reproducible. Just open whatever webkit based browser you want, and keep reloading the same moderately big page. Ram goes up, never to return. That works with a trivial program that embeds webkit via gtk, too. Or you can just look at the commits on webkit: a couple of leaks fixes every week.

Good thing Chrome kills the entire process hosting a tab when you close it.