for (var a in ww.mode.modes) { var b = ww.mode.modes[a].pattern; var c = b != null ? b.toString(2) : ''; console.log(a, b, c.length > 0 ? Array(9 - c.length).join('0') + c : ''); }

http://www.eclipse.org/cdt/

I no longer use Firefox and have long since switched to Chrome, but in doing so my bookmarks have become effectively useless. What I mean by this is, in Firefox, one of the greatest (and probably underused) features was the ability to tag individual bookmarks instead of simply pushing them into a single folder.

This meant that, when I wanted to revisit a bookmark later on, I simply had to start typing in the tags (which I always made broad and diverse). By typing in more and more tags that I thought would likely relate to the article I wanted to reach, it would narrow it down. I never had to remember what the article was called, or where it was, or anything like that.

Now if this automatically happened while bookmarking? Some intelligent manner in which the page could be skimmed for keywords or something. Bookmarking and retrieval becomes much simpler...

Just wanted to throw that out as something to consider :)

(Now, one Chrome, I usually just leave tabs open or try to organize into folders and fail miserably :/ )

As for the iPhone vs Android thing, the graph used by OP is a bit misleading (it's restricted to AUS only). I'd take a look at these ones instead: http://gs.statcounter.com/#mobile_browser-ww-monthly-201108-... or http://gs.statcounter.com/#mobile_os-ww-monthly-201108-20120... for worldwide.

I guess he's trying to highlight how it's different in different places around the world though.

Sure the OP advocates "set and forget", but it seems simply silly to do this indefinitely. Obviously, after a while, you're going to want to check in on the results and prune out low performers.

Is that not the entire point of all these different testing methodologies to begin with?

Also, if you were to follow the same "set and forget" strategy with A/B, you'd have a 50% chance of showing the 0% CR design, where-as it's only 10% with this method.

Seems like it wins out in both cases to me.

That said, I really do wish there was better browser support for them. Having to embed them as objects instead of images, for example, is a tad bit lame :/ And then you're still left with anything before IE9 (I think?) unable to see them. On the mobile-end, the same goes with anything before Android 3... Or weird buggy behaviour when you're applying things like hover effects to parts of the image, etc...

It's definitely promising though

1) Try a different theme, it may help if it really affects you that much. But this is the only one I somewhat agree with as being possibly an issue; but nothing I really thought of when first looking at the new UI

2) The marker is more than far enough away to make it easy to scan through IMO. This feels far too subjective to just throw out and be like "yea this is definitely a bad change" without doing some testing first. Either way, you can disable this from settings. (Disable snippets iirc?)

3) This too can be disabled: go to settings and change it to text labels instead of graphical labels?

As much as I used to hate the new look too, I think it's improved enough since its first iteration to get out of the way and let me do my thing. Though, I still REALLY hate the fact that you can't click on the "Google" logo at the top left to go back to the main page for whatever application you happen to be at. I have no idea why they would remove that...