I’ve been using Chrome exclusively for roughly the past six months, before that it was Safari. Needless to say I’m a big WebKit fan. I didn’t become one until moving to OS X, before that I was a die hard Firefox user when I ran Linux. I remember first stumbling upon Firebug and it was a glorious day. That extension completely changed the way I built websites. When WebKit first came out with the redesigned version of Web Inspector, I was thrilled. Front end development just got totally awesome in both Gecko and WebKit.
Admittedly, the aesthetic of WebKit’s Web Inspector had a draw on me, I loved it. The only problem was Safari’s release cycle. Sure there were WebKit Nightlies but… they’re nightlies. I need to test in browsers that are actually being used. Then came Chrome. A faster release cycle with an updated Web Inspector every time. That’s been my story for the past number of months. There’s no getting around the fact that Firefox’s performance on OS X leaves a bit to be desired when compared to Linux and Windows. I was happy with Chrome. Then the geniuses behind Firebug go and do something like this:
Smitten. Instead of the same old
console.log you can fancy pants
console.table your data.
That’s just one of the new features coming to Firebug 1.6, but it’s one that has my attention. The browser market is a cutthroat (in a great way) brotherhood, and it’s awesome. I love the fact that I can’t make it six months without thinking about switching browsers. Best of all, there’s only good coming from the competition.
[…] This post was mentioned on Twitter by Jonathan Christopher, JR Tashjian. JR Tashjian said: RT @jchristopher: Dude. console.table() looks preeettty sweet https://jonchristopher.us/2010/12/01/whats-new-in-firebug-1-6/ […]