mattgaidica

Yea, I am sure there is some top secret Google magic if they are forced through SSL!

Yea, luckily nearly every major API and service (Amazon, Facebook, Google..) has an encrypted version to pull from. So as long as the entire team understands that, then I only have the usability issue as an argument. If we could get GoDaddy and other hosts to have like a $10 "Add SSL" feature, I think we would see a really good adoption of it being the standard!

Encrypting site content increases server load, so response time may lack a little.. and we all know Google does take that into account. Also, it might be important that robot files and sitemaps are under the https protocol. I am guessing Google is pretty darn smart about it, I can only imagine though that a broken certificate throws a red flag.

I am 100% with that mentality, I guess I just see the overhead and understanding of HTTPS causing more problems in practice than solutions for developers who are not security-centric. Think we'll ever see google.com go to SSL?

No. I think the HTTPS in the browser prompts a user to think there is confidential information being passed when your just browsing, so now your break user experience. The app portion could be, and should be for any semi-secret information, but keep the front-end clear of it. Plus any and all external resources in-page must be https, it might hang you or a designer up down the road and break your cert.