4 ms·
> 1. Metcalfe's original Ethernet has been replaced a bunch of times... These replacements were seemless to users. New Ethernet adapters were compatible with a
by DecoPerson 7y ago
> 1. Metcalfe's original Ethernet has been replaced a bunch of times...
These replacements were seemless to users. New Ethernet adapters were compatible with at least the previous spec. The Git import/export of Fossil is not seemless at all. It actually adds quite a bit of complexity if you want to introduce it your regular workflow.
> 2. Microsoft's long-term stalwarts Windows and Office are dying...
Citation needed.
> 3. Adobe's having a hard time hanging onto its old market...
Citation needed.
> 4. IPv4 still won't go away...
There is a lot of hardware out there that only works with IPv4. The costs and risks of switching your org's internals, product or services from IPv4 to IPv6 are phenomenally higher than switching your org from Git to Fossil or adding Fossil support to your product or service.
If Fossil is truly superior to Git and people are not switching to it, then there's no hope they'll switch to IPv6. Not until the cost of not switching is greater.
- chx 7y ago> These replacements were seemless to users. Not at all. I remember how long it took for Cat 5 to replace thinnet.
- fulafel 7y agoWifi mostly replaced ethernet for user facing applications. There was partial protocol compatibility between ethernet and wifi, but the user experience was very different. Some features were lost or degraded (eg speed, reliability, security, configuration complexity) but a pain point (cables) was fixed.