I personally use Chrome and I teach a class that involves some lessons on HTTP/web scraping/web app dev and I ask the class to use Chrome. For me, my bias is towards how much I like Chrome's dev tools, though I haven't used Firefox's in awhile. The ease of creating multiple browser profiles is great, too, though I hear FF has the same thing. I'm not much of a plugin user, but I'll be using Chrome's Secure Shell [0] f…
Can it be said that your bias is purely based on the familiarity? Yes, Firefox has multiple profiles. Putting "all your eggs in one basket" in security context is suspicious. For SSH, Putty is a small program compared to the whole Chrome, security-wise much easier to evaluate. I don't know how using Chrome for SSH can be rationalized. Who is behind of that "Secure Shell" plugin ("offered by chrome-secure-shell-publis…
As for my class, yes, I'm not enthusiastic about shelling from the browser no matter how many people like it. But the main mitigation is that the class work we do is based off of my AWS setup: I spin up the EC2 instances and I manage/distribute the keys. None of the assignments require using their own personal info. And another reason for teaching them how to use browser profiles (something I've never seen students have set up) is so that they if they want to build something with Twitter's API, i can strongly advise for them to make a fake account and operate it in a different profile, to prevent accidental Twitter snafus (among other problems).
Why Chrome shell over PuTTY? I remember struggling with things like copy and paste, to the point where I think it is easier to use the mouse...but I push students pretty hard on using the mouse as little as possible. Chrome Shell feels as close to the OSX Terminal with the exception of key handling and the inability to access or transfer files from your own system.