3 ms·

I was the same, but eventually Chrome's slowness and resource-intensiveness (this is on OS X, of course) drove me to Safari. Chrome is still my 'dev' browser t

• paulojreis 11y ago
  That's my setup, essentially. Chrome as my 'dev' browser, as I'm too familiar with its devs tools. Another nice thing about having a browser only for development is that, when you're demo'ing, there's less of a risk to show unwanted stuff (e.g. address bar suggestions). :)
  • culturestate 11y ago
    > Another nice thing about having a browser only for development is that, when you're demo'ing, there's less of a risk to show unwanted stuff I go a little further and use distinct Chrome profiles for every project to avoid this. It also helps to keep saved credentials for e.g. client-specific SaaS accounts separate without commingling them with my own 1Password vault. *I know 1Password now supports multiple vaults, but I haven't had a chance to try that workflow yet.