While reading the disclaimers, note that this is a set of disclaimers on a software development kit labelled beta. You should not be using this for production. Period. And if you do, then Microsoft should not be liable.

So I don't mind those terms. If they remained when the product shipped (and some likely will) then I would mind them. But not now.

But the anti Open Source games are a different kettle of fish. I often say that I like using the right tool for the job. However if Microsoft wants to ban the use of things like Emacs, CVS, Perl, Python, Ruby, cygwin, VNC, and so on, then the right tool for me is going to be very unlikely to be from Microsoft. That kind of restriction is simply not acceptable.

In reply to Re (tilly) 2: Microsoft is against Perl!? by tilly
in thread Microsoft is against Perl!? by tilly

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.