3 ms·
Spending 16 years in development is also not an amazing look, but if we run with that - no, 45% adoption after 12 years certainly is bad. As a reference point,
by yjftsjthsd-h 3y ago
Spending 16 years in development is also not an amazing look, but if we run with that - no, 45% adoption after 12 years certainly is bad. As a reference point, it looks like Cisco gear has a ~5 year process for EOLing things. So 12 years is a while, even if it was purely driven by old gear getting replaced.
Edit: I should caveat - I don't have good data on actual lifespan of networking equipment; if you can show that it's likely to live more than a decade then that would be reasonably compelling.
- orangeboats 3y agoTo Google, HTTPS was at 48% adoption in 2014. [0] This is 14 years after its initial specification (RFC 2818), even longer if you take Netscape into account. And this is despite the fact that HTTPS is completely done in software, which typically gets updated more often than hardware. I stand by my assessment that 45% adoption after 12 years is actually pretty good. [0]: https://transparencyreport.google.com/https/overview?hl=en https://transparencyreport.google.com/https/overview?hl=en (I use Google's data for both HTTPS and IPv6 stats. If you consider 3rd party data, HTTPS adoption is way worse, even to this day it hasn't topped 75%.)