Beyond those two I still don't see any evidence that other Win32 API modules are absolutely necesary to the Perl toolchain, and that they can't just be installed later like any other module.

Seriously Adam, how well do you know the API? Ive read elsewhere that youve stated that you arent a C programmer and aren't a Win32 developer, so on what basis do you form that conclusion?

I mean I can think of a variety of places where proper API support would be useful. Consider a module I've seen you discuss elsewhere, Term::Readline::Perl, if Win32::Console was core then the possibility that TRP could be made fully functional on Win32 Perl would be much higher.

I think there is a clear reluctance in p5p to put dependencies on non-core modules into core modules, so im doubtful that route is very useful. Even if we assume people do go the "Win32 support is optional" route (they havent really so far) I reckon at some point there will be so much cruft in the core code checking for proper Win32 support that I reckon it will outweigh just bundling the modules into core anyway. And as far as I can see the only valid reason proper Win32 support is omitted from core is distribution size, which itself actually would only affect the handful of people regularly working on core. (I think the true reason is actually just that there is a certain amount of prejudice and ambivalence towards the platform in the p5p group).

Anyway, you seem to really like the "no special flower" comment, so I'll throw one back at you: One size does not fit all. Everything has special needs, and thats ok. The world would be a very bland and boring place if there were "no special flowers".

And as a last follow up, for all my comments, please dont think that I dont support what you are doing with Vanilla Perl and Strawbery Perl. I do support it1 . I think its a breath of fresh air in the Win32 Perl scene and i think long term it will achieve a lot of good things. So thanks a lot.

1. except the name, I hate the name "Strawberry Perl", why not White-Perl and Blue-Perl or something that is at least shorter to type?

---
$world=~s/war/peace/g

In reply to Re^4: [JOB] The Perl Foundation seeks Windows Developer by demerphq
in thread [JOB] The Perl Foundation seeks Windows Developer by adamk

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.