Hacker News Reader

We did. :)

For anybody who's tracking, we're up to 140+ folks, and the spreadsheet has moved into high-traffic mode. Thanks all - this will be great and I'm happy for it to be linked from a more permanent location.

scottruon HN Contractors: Add Yourself

BTW, I will clean up some disorganization once the editing slows down.

scottruon HN Contractors: Add Yourself

Right, thanks to the anonymous person who fixed it. I'm trying to keep an eye on it.

scottruon HN Contractors: Add Yourself

Thanks. I thought about that, I just thought we'd get more participation (and more consistency) if people saw what others were saying, and I trusted the group (which seems to have mostly worked).

scottruon A/Bingo: OSS Ruby on Rails A/B Testing. No Javascript. Two lines of code.

I'm a very active GWO user. I haven't tested A/Bingo yet, but based on the description, there's one other advantage you have: I don't have to rewrite erb as javascript in order to execute various tests.

If a lot of your view layer is written in erb (likely b/c it's not javascript-heavy), then to use GWO, you have to basically rewrite all of it in js, since GWO dynamically inserts client-side code into the spots you specify.

So if you have a display loop that uses a bunch of object properties in your erb, for example, you have to copy those objects/values to js variables and move the loop to js. It's all doable, it's just very non-DRY and just altogether unpleasant.

(The other option with GWO is to use the Javascript to load partials, which I do now, but which has some unusual properties, like lazy loading.)

Having the a/b decision be server-side is a nice thing. I'm looking forward to trying it out.

(Also, not having to pull out piles of GWO code every time is a nice thing too.)