5 ms·
The fact that it allowed for all kinds of topologies, and that it served as a bus (shared medium, hence the name 'Ether') rather than a point-to-point link is w
by jacquesm 4y ago
The fact that it allowed for all kinds of topologies, and that it served as a bus (shared medium, hence the name 'Ether') rather than a point-to-point link is what I think made the biggest difference.
Of course now that we all use switched links they are point-to-point again but an ethernet 'hub' gave you the same effect as a bus with all devices seeing all of the traffic. This made efficient broadcast protocols possible and also allowed for a historical - but interesting - trick: the screw-on taps that you could place on a single coaxial cable running down a department giving instant access without pulling another cable. Zero network configuration required, just get the tap in place and assign a new address. DHCP later took care of that need as well.
This was fraught with problems, for instance a single transceiver going haywire could make a whole segment unusable and good luck finding the culprit. But compared to the competition it absolutely rocked.
- em-bee 4y agofor years i was carrying around an ethernet splitter that would allow me to connect two devices into one ethernet port. i last used it some 10 years ago in a place without wifi
- asimpletune 4y agoYeah, it’s a very cool trick that surprises a lot of people when they learn that only half the wires are used.
- jacquesm 4y agoNot for gigabit ethernet and good luck picking up the pieces if you find yourself splitting a power-over-ethernet setup :)
- bombcar 4y agoReminds me of the "REAL" power over ethernet: http://www.fiftythree.org/etherkiller/ http://www.fiftythree.org/etherkiller/
- jacquesm 4y agoHehe, I remember that page :) Thanks! Some of the captions are quite funny.
- em-bee 4y agousing a splitter is usually a temporary solution, and i am unlikely to be sharing a port with a PoE device. nor do i care about gigabit speed when the only reason to use a splitter is to make up for missing wifi.
- ethbr0 4y agoTo build on your comment, although it's been years since I studied Ethernet in depth... - (On the bus thread) Ethernet started from an assumption of bad behavior (out of spec cabling, misbehaving clients, etc.) and tighten requirements just enough to construct a useful network. Much better balance between de facto ruggedness vs performance than its peers. - From the beginning, Ethernet reasoned that it was cheaper to put logic in purpose-built networking hardware than endpoints (i.e. PC network adapters). This was a better scaling tradeoff. 1x $$$ network device + 100x $ client adapter vs 1x $$ networking device + 100x $$ client adapter. - Because of the above, you started to get really cost- and data-efficient networks when the cost of Ethernet switches plummeted. (Remember, in early Ethernet days, networks were hub/broadcast-only!)
- jacquesm 4y agoI remember paying about $1000 per port for 100 megabit switches.
- ethbr0 4y agoHa! But they delivered that much value (or more), so the market supported the price until supply flooded. We could do worse for a transformative technology ranking metric than "How overpriced was this when first released?" (significant look at Nvidia cards)
- jacquesm 4y agoI had a bunch of workloads that quite literally got cut down to about 15% or so of the original runtime (a cluster compressing a whole archive of CDs for a large broadcaster) so I happily paid up. But still... $1000 / port!! And here I have sitting next to me a 48 port gigabit switch that cost 15% of what that 100 megabit switch cost in 1996 or so. Iirc it was one of the first D-link products I bought, it definitely wasn't great (it ran pretty hot) but it worked quite well enough. Amazing progress.
- bombcar 4y ago
- gooroo 4y agoAnd it was sniffing heaven. Only paralleled by the brief period of nobody using any serious encryption on their wifi.
- sriram_sun 4y agoYup! A whole other real-time industrial protocol called EtherCAT has been built on top of the same hardware.