Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Beg to differ.

An OS isn't so much a tool as a toolbox. The OS will hold the tools themselves (perl, Office, Quake), and the accessories that make those tools usable (lib files, device drivers, logging mechanisms), but the OS itself does very little.

Extending our toolbox metaphor, imagine you have a whole bunch of tools that need different power cords (9 volt, 12 volt, 220 volt). Windows replaces them with a single monster cord that will accept any voltage and self-adjust. Linux allows you to see each and every cord and select for yourself. 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.

If you're prepared to do some work, you can use one and only one OS. You will, however, have to make some sacrifices. If you refuse to have a Windows box in the house, you won't get to play most PC games. If you feel that gaming peaked with Tetris or you already own a Playstation, this won't be an issue for you. If you use Linux, you'll save a few hundred dollars by using free software, but there will be a learning curve. If you enjoy the learning process, great! You have a project, and there's hours of fun awaiting you. If all you want to do is type a simple letter and read your email, it's probably worth a few hundred dollars to avoid the hassle.

If, however, you're a civil libertarian, there are many "features" in Windows that would terrify you. In that case, go with Linux.

"What do I want? I'm an American. I want more."

In reply to Re: Re: OT: Switching Sides by logan
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
    [Corion]: ... or so I think. As I said, I'm somewhat vague on how to make AnyEvent cooperate with a callback-driven IO event loop that gives me callbacks when data is available or can be written
    [ambrus]: what push_write thing? I don't think you need that. that's implemented generically by AnyEvent::Handle
    [Corion]: ambrus: Yeah, that's what I think as well. But you give me an idea, maybe I should start with implementing the timer, as that should be far simpler and with fewer edge-cases/nasty interaction than the file watcher
    [ambrus]: You only provide the watcher part that tells when the handle is readable or writable, not the actual writing and reading.
    [Corion]: ambrus: Hmmm. It makes sense that AnyEvent would implement the push_write itself, but I think I don't have a good idea of where the boundary between AnyEvent and the underlying event system lies... Implementing the timer should give me a better idea
    [ambrus]: Corion: push_write is in the higher level abstraction of AnyEvent::Handle, not in the watcher
    [Corion]: ambrus: Hmm - rereading Prima::File, that merrily coincides with what Prima does - it tells you "you can read", and you're supposed to read from the fh yourself. I thought it called you with the data already read, which would've been harder to integrate
    [ambrus]: you just need an io watcher, created by &AnyEvent::Impl:: Whatever::io(...)
    [Corion]: So after talking it through with you even while I'm still not entirely clear on where AE ends and my implementation begins, I think I understand that I only need to implement some smaller parts for each functionality I want to support.
    [Corion]: Yeah... and you might even be able to mix and match additional functionality if you have additional async suppliers, like from a separate thread

    How do I use this? | Other CB clients
    Other Users?
    Others chilling in the Monastery: (8)
    As of 2016-12-08 12:21 GMT
    Find Nodes?
      Voting Booth?
      On a regular basis, I'm most likely to spy upon:

      Results (141 votes). Check out past polls.