If MS tell them that in order to upgrade their 1000s of workstations, they will also have to re-write every application they use; or apply in writing to MS (or any 3rd party body), to have their existing in-house and 3rd party applications 'signed off', the impact of the upgrade would just be too costly and too risky to contemplate.

Can you imagine every bank, government dept. etc., having to supply the source code of their proprietary and commercially sensitive applications to MS or some 3rd party clearing house organisation before they can run them?

You've got to think like a salesman. Present it as an opportunity. Now the IS department can finally enforce all of its regulations on which software is officially approved for use. No more worries about viruses/trojans. No more employees goofing off playing computer games. And it won't be any more of a burden to implement this, than it currently is to negotiate their site license. Banks and governments are the first customers who would sign up for this feature. Rogue bank employees won't be able to sell internal/sensitive documents, because they'll only be decryptable on authorized bank computers. Government beauracrats will be less able to leak stuff to the press. And MS won't go to the bother of trying to certify that the custom programs you want signed are reliable. They'll just have a rubber stamp approval for any binary you submit. Of course, you'll get to pay for the priveledge. And they'll be running as second class citizens, without full access to every part of the system, otherwise you could possibly compromise the whole scheme. But it'll mostly work.

In reply to Re^6: Future of Perl on Win32? by Anonymous Monk
in thread Future of Perl on Win32? by bowei_99

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.