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.)
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.)