• aard@kyu.de
      link
      fedilink
      arrow-up
      31
      ·
      1 year ago

      It wasn’t really a replacement - Ethernet was never tied to specific media, and various cabling standards coexisted for a long time. For about a decade you had 10baseT, 10base2, 10base5 and 10baseF deployments in parallel.

      I guess when you mention coax you’re thinking about 10base2 - the thin black cables with T-pieces end terminator plugs common in home setups - which only arrived shortly before 10baseT. The first commercially available cabling was 10base5 - those thick yellow cables you’d attach a system to with AUI transceivers. Which still were around as backbone cables in some places until the early 00s.

      The really big change in network infrastructure was the introduction of switches instead of hubs - before that you had a collision domain spanning the complete network, now the collision domain was reduced to two devices. Which improved responsiveness of loaded networks to the point where many started switching over from token ring - which in later years also commonly was run over twisted pair, so in many cases switching was possible without touching the cables.

    • AmberPrince@kbin.social
      link
      fedilink
      arrow-up
      21
      arrow-down
      1
      ·
      1 year ago

      To be pedantic: Ethernet is a protocol so mentioning the medium used outside of a historical context is kinda irrelevant.

      • ajlanes@thegoatery.dyndns.org
        link
        fedilink
        arrow-up
        2
        arrow-down
        2
        ·
        1 year ago

        @@kbin.social A history plaque and its additional explanatory text is surely exactly the historical context to mention things like medium?

        • AmberPrince@kbin.social
          link
          fedilink
          arrow-up
          5
          ·
          1 year ago

          And it did. It started with coaxial. The fact that ethernet is now largely used in conjunction with UTP or STP doesn’t add much when talking about the Ethernet protocol itself.

    • r00ty@kbin.life
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      Ah, the good old days of network troubleshooting. Wiggle the cable at the BNC connector until the whole segment comes back to life. Those huge repeater boxes with like 8 ports. Somehow 10Mbit to a Netware server being faster than a local hard drive. Smartdrv fixed most of that though.

    • RaccoonnOP
      link
      fedilink
      arrow-up
      4
      arrow-down
      1
      ·
      1 year ago

      I never even realised that. Thanks for mentioning it…