I did the ff-chrome-ff switcheroo a number of times. Now I generally use both: I find that chrome is a snappier startup and has a better flash runtime (since it does its own rather than relying on adobe). Firefox is more stable / uses less memory for a larger number of tabs.
I do believe in the mozilla mission for an open web, and it's got fairly comparable performance overall, so I use it for my main browsing / firebug. Chrome's for flash-heavy sites and playing with webrtc occasionally.
Inspector on chrome has certainly become quite good -- I've missed firebug less and less over time as I started using it. Though Firefox's new built-in developer tools are really sweet and might add enough functionality for me to miss in the near future. They're adding a command line thing that is super cool!!
I may be over-thinking this, but in case you didn't know, Flash Player in Chrome is still developed mostly by Adobe. Chrome has a different plugin API, I think, and some extra sandboxing, but the core parts of Flash Player in all browsers come from the same Adobe-owned codebase, including Chrome's bundled version.
I find this true as well. Right now I have Chrome open with a number of JS heavy tabs (gmail, analytical, Wordpress dashboard because it apparently hates Firefox). I'll also open up Youtube videos on Chrome because Firefox is always laggy with flash videos.
But the bulk of my tabs are open in Firefox, and I prefer Firebug over the Chrome console for development
I do believe in the mozilla mission for an open web, and it's got fairly comparable performance overall, so I use it for my main browsing / firebug. Chrome's for flash-heavy sites and playing with webrtc occasionally.
Inspector on chrome has certainly become quite good -- I've missed firebug less and less over time as I started using it. Though Firefox's new built-in developer tools are really sweet and might add enough functionality for me to miss in the near future. They're adding a command line thing that is super cool!!