This is utter BS. ECC is done in the memory controller. The underlying software need not even know it is there unless it wants to look at error stats/respond to error events.
The software I am referring to is status monitoring and fault handlers / responding to unrecoverable errors. Most of this software is kind of quietly forgotten, niche and may not be executed often.
I do believe that ECC scrubbing can now be done automatically by the memory controller.
As an Ethernet pipe gets upwards of 70% saturated the whole thing starts to collapse because so many of the nodes are colliding and re-trying that your available bandwidth goes down the toilet.
Not sure if you were talking about the 80s, but today we have more than just hubs, we also have bridges/switches/(routers), which limit the collision domain to the two Ethernet endpoints, so generally the bandwidth lost due to CSMA/CD has been limited to the worse case CSMA/CD when N=2.
Factorials were someone's attempt to make math LOOK exciting.