...but it's a bore to set up.""@"

I don't think that makes much sense, even if the browser is smart enough to render a color between #000001 and #000002 during the transition, we certainly won't notice it.

I think a lot of people are considering GitHub as a service to store and manage the revisions in PSD files due to their recent PSD preview feature.

It's a cool feature, but it's a bit misleading imo. Git is not particularly well suited for binary files, it stores diffs for every revision in your working copy, and you download them all when you clone a repository. This means that your repo will grow dramatically in disk usage, and cloning a repo becomes painfully slow.

Contrast that with LayerVault and similars, where you get only the latest revision in your hard drive.

It works as expected in Chrome, you can try it. I agree breakpoints are the way to go in most situations, but something so fundamental as logging should be better engineered.

Safari. That said, there's one thing that drives me up the wall: console.log in Safari is asynchronous, meaning that if you try to log a non-primitive (arrays, objects) what is logged might not be the current values at the time of the console.log call. I'm REALLY hoping Yosemite fixes that.

Before that I was a Chrome user, but I got really fed up with their obnoxious, slow-loading and mandatory "New Tab Page".

I'd say Alfred strength lies in the extensibility rather than just screen position, but yeah...first thing that came to my mind as well.

Your client probably wants to keep the maintainability of the project as simple as possible, so that their devs can quickly iterate over their current system using the visual identity that you're designing for them after your contract ended.

I'm familiar with Batarang, it was the original inspiration. I wanted that functionality in browsers other than Chrome, while also addressing my own insatisfaction with its UI/UX.

The first version supported Safari only, as it had the biggest deficit in AngularJS tooling, and it's a browser I otherwise enjoy. Chrome was next as it's the most popular and I kept getting a lot of requests for it - kind of a surprise because of Batarang. It seems a lot of people favoured ng-inspector over Batarang for the design, which was uplifting :)

Turns out starting with Safari was perfect, as it has the most limited extension API of the three. After Safari, the other browsers were much easier to target with the existing code base.

This is so cool. The author also shared the his WebGL globe implementation as a component: github.com/arscan/encom-globe