Well written. But some harsh words in there for the new DevOps, microservices nirvana :-) ++ anyway!

Kidding aside, I don't think it's all that bad ... although 20+ years as a network engineer, I've seen a lot of wheels re-invented and lots of the Docker, Kubernetes, microservices ecosystems re-invents a lot - like DNS and overlay networking. I'm all for change if it makes things better, but change for change's sake - I (and I think the collective "we") can do without.

I always lament the biggest advancement in network automation over the past 20 years is moving from screen-scraping Telnet with Perl to screen-scraping SSH with Python. Not that I'm down on Ansible, it provides way more than my little Perl script (better templating, more device support, etc.) but the software abstraction band-aid did not solve the underlying problem - network devices do not have a common language. Maybe the Ansible development effort would have been time better spent in pushing forward NETCONF or similar open standards for network device data model abstraction instead of interface abstraction.

Cheers.

In reply to Re: Why Perl in 2020 by VinsWorldcom
in thread Why Perl in 2020 by ait

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.