4 ms·
People are lazy and will wait for absolutely the last moment: "why should I spend time configuring my network when I still can purchase IPv4?" This was especial
by takeda 9y ago
People are lazy and will wait for absolutely the last moment: "why should I spend time configuring my network when I still can purchase IPv4?" This was especially bad because vendors and ISPs had the same attitude, so even when there was someone willing to do the work, those parties stayed in the way.
I actually see great parallels about Python 2 vs 3. The changes between these versions aren't really big, and converting is not that hard. Other languages already did it many times (Ruby actually did it when switching from 1.8 to 1.9, but people moved on quickly, because if they didn't, their apps and libraries no longer would work and no one would use them).
IMHO the real cause was that Python gave a lot of time to do it (nearly 15 years!), but there was no real interest in Py3 until 2015 when Python 2.7 went into maintenance mode (no new features backported, BTW all features of Python 2.7 were backports of Python 3, fueling "Python 3 doesn't have anything new, what should I switch?"), and organizations most likey will wait until 2020 (EOL) to port their applications.
- briffle 9y agoI was a charter business fiber customer for 5 years. (multiple sites in multiple states) I asked every few months, got relayed to the same web page sayings "its rollout is planned in Q4" (for 5 years it said that, never included the year) and gave instructions on how to setup the single 6RD server they had in St. Louis. They merged with a few other cable companies, who had working ipv6, but nobody could give me timelines. We had customers wanting to access our applications via IPV6. We actually had to setup a remote proxy on an IPv6 network to then proxy back over IPv4. I left that job a year ago, so perhaps Charter has had a huge change of heart, but I strongly doubt it.