26 ms·
HTTPS is not rigid and costly for a single connection. It's rigid and costly because it prevents simple options for caching like sharing google hosted jquery. Y
by kevinpet 14y ago
HTTPS is not rigid and costly for a single connection. It's rigid and costly because it prevents simple options for caching like sharing google hosted jquery. You can still use a CDN, but then you have more complexity in managing your certificates and pay 1/3 more (Cloudfront pricing).
HTTPS is manageable where needed for security. Sleazy ISPs are making it necessary even where security is not a concern -- for example, viewing Apple's homepage.
- cmelbye 14y agoThat's not true. Google seamlessly supports both HTTP and HTTPS, and many other sites do too through simply using // as the protocol.
- iy56 14y agoThey are not making it necessary, only convenient. You're not harmed by seeing a few ads.
- brandon272 14y agoThis point of view assumes that the injected code is harmless and never causes compatibility issues when viewing a website. The moment a JavaScript conflict occurs and Apple loses a sale or the ability to buy a product online is hindered, I think that there will be parties who certainly feel they are being "harmed" by this process of manipulating the content being delivered to end users.
- iy56 14y agoYes, this technique could potentially be misused. You can say the same thing about any technology.
- driverdan 14y agoUsing 3rd party CDNs, like Google Hosted Libraries, are often slower anyway. http://www.stevesouders.com/blog/2013/03/18/http-archive-jquery/ http://www.stevesouders.com/blog/2013/03/18/http-archive-jqu...