Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl Monk, Perl Meditation

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
The upside on the Windows approach is that you can't get it wrong because the decisions are out of your hands. The downside is that this self-adjusting sacrifices stabilty and the ability to self-diagnose. The upside for Linux is that you can see all the cords and decide for yourself. The downside is that it won't stop you from picking the wrong one and screwing things up hardcore.

While I agree with your sentiment and upvoted your node, I have big disagreements with this analogy.

Maybe "you can't get it wrong" with Windows, but you can rest assured that Windows will get it wrong for you on occasion. And when Windows screws things up hardcore for you, it'll mean re-installing the whole damn thing. But, with Linux (or Unix), things getting that hosed are pretty unlikely. And when they do, you can rest assured that it was probably the result of something stupid that you did. That means it's something you can prevent next time. I much prefer that to the cross-your-fingers-and-try-again method required of Windows users.

Some might argue that they'd rather just spend an hour or two re-installing than spend half a day trying to fix something they broke. I understand that reasoning, but it is short sighted. In five years, such a person will still be re-installing anytime something breaks (which will be just as often as before.) Meanwhile, some who is willing to figure out what went wrong and fix it will have gained oodles of experience that will help them to both fix errors more quickly and prevent them in the first place.

In other words, with Linux (or Unix) you get 5 years of experience. With Windows, you get 1 year of experience 5 times over.

"My two cents aren't worth a dime.";

In reply to Re: Re: Re: OT: Switching Sides by sauoq
in thread OT: Switching Sides by Khansultant

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and a log crumbles through the grate...

    How do I use this? | Other CB clients
    Other Users?
    Others drinking their drinks and smoking their pipes about the Monastery: (5)
    As of 2018-06-24 21:34 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (126 votes). Check out past polls.