The analogy of a divorce is a good one, however I think it's premature. There is no cheating, no plundering of the bank account, no kidnapping of the kids (or worse).

I do like how you've broken it down. In those terms I am decidedly in the SAAT camp. But I love my hammer, and with it everything is a nail.

We need to stay together for the kids, and this is not some naive pollyannish view or line about Catholic GuiltTM. To many coding communities have become broken homes (PHP, Python, etc) with one left to choose which parent to live with. Too many others have died in utero or been prematurely aborted or abandoned before gaining the ability to fend for themselves or have a mature outlook on life.

Somehow perl must remain perl, yet progress. I don't care if you call it 5.x or 7.x. I do care that there is and always will be the One True InterpreterTM on any system, even if it won't run my shitty line noise I hacked together in a fit one night.

And being part of the SAAT camp, I am part of my grandfather's camp. I prefer to slow down and look backwards, not forwards. I reject shiny things. I like his hammer. It's made of real steel and rock hard hickory. It's never had to be re-headed. I mock hammers sold at Walmart that are made in China and fail after 1 year. Preferring the latter is no different than immature javascript fanbois who don't realize what they're tossing away when they jump from fad to fad .. or to Rust. Or whatever. You lose a little bit of power in your tools (and yourself) every time you do that. I treasure perl just like I treasure my grandfathers tools. Be careful what you toss out and replace with a cheap product in pursuit of some modernity. You will lose every time.

Why did "perl 6" fail to replace the True InterpreterTM? Because people forgot about things like this, http://perlbin.sourceforge.net/perlcompiler/perl.internals.pdf, and the collective power and wisdom that was present back then (and thankfully remains strongly today).

Another adage that they say about divorce it that it really just results in everyone but the blood sucking lawyers losing. And they get richer. And it costs each parter just as much to live alone as it does together, even more so when kids are involved. In this case we'd risk throwing away a beautiful life built on strong fundamentals and collective wisdom. As they say, the bones are GOOD. We can work with this.

Let's stay together. for the kids.

---

update - fixed minor spelling and formatting

In reply to Re: Amicable divorce by perlfan
in thread Amicable divorce by ribasushi

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.