<html><head></head><body>Or, the short version of my favorite design precept: "get the glue right".<br><br>This can be as trivial as if you have video to push out of a device, use analog VGA unless there is a compelling reason not to.<br><br><div class="gmail_quote">On August 1, 2019 2:29:24 PM EDT, Jeremy Chadwick <jdc@koitsu.org> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On Thu, Aug 01, 2019 at 01:02:37PM -0500, Eric Spaeth wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">On Wed, Jul 31, 2019 at 2:11 PM Scott Weeks <surfer@mauigateway.com> wrote:<br><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"><hr> and uses RIPv2 to announce its LAN-side IPv4 block<hr> They use what!?!?! :)<br><br><br></blockquote>The right protocol for the job.<br></blockquote><br>I suspect the "they use what?!?!" comment is driven by the age-old<br>mentality of "RIPv1/v2? OMG who uses that, nobody uses that, it's old,<br>limited hop count, it uses multicast, it's terrible, it should be<br>replaced then taken out back and shot!"<br><br>This overall belief is a very broken one, yet continues to rise/bloat in<br>the day and age where everyone wants "new shiny" and thinks "newer is<br>better". I've seen similar reactions to all sorts of late<br>ARPA/DARPA-era protocols, even ones as "basic" (except not really) as<br>telnet. Rarely is good/solid technical justification given for this,<br>instead it seems to be driven by dislike for having to read RFCs and<br>disapproval towards all things "old".<br><br>More rarely is consideration given to the fact that something is used<br>because it is technically better/more relevant to the situation (such as<br>here), or because it's substantially more well-understood (this latter<br>point is often overlooked. Example: syslog has some shortcomings (see:<br>RELP wrapper), but it is a well-understood protocol and is a lot easier<br>to troubleshoot comparatively to things like, say, logstash). I am not<br>implying alternate or newer routing protocols are not well-understood, I<br>am speaking about the mindset.<br><br>Picking the right tool (protocol) for the job is the proper approach, no<br>matter how "old" it may be. I wish more people asked "why was {thing}<br>chosen and when?" first. The why, as demonstrated here, is important.<br>Because newer is not always better.<br><br></soapbox><br></pre></blockquote></div><br>-- <br>Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>