in reply to Improving CPAN using Google sidewiki

Um, maybe try posting this again in the future ... when sidewiki supports more than just Windows/ia32. Those of us running anything else don't get to take advantage of your wiki contributes, but we can take advantage of, and contribute to, the annotations that annocpan provide.

Update: My initial problem was trying to install from the google.com/sidewiki site. That didn't work so hot. After some googling, I found the beta toolbar that works. Of course, that brings up a new way to reach the same conclusion: it's beta. And this is the toolbar here - something not normally in beta. At least wait until the toolbar is stabilised before trying to get the Perl community to commit to it. Try it out, sure, but commit to it? Not so much.

  • Comment on Re: Improving CPAN using Google sidewiki

Replies are listed 'Best First'.
Re^2: Improving CPAN using Google sidewiki
by EvanCarroll (Chaplain) on Sep 28, 2009 at 18:50 UTC
    I know it works for 32bit Firefox/Linux. And, I'm tempted to say it works for 64bit Firefox/Linux too. Other than that, you're talking about a /very/ small percentage of perl *developers* -- not end users of the modules: I make my stuff on 32-bit Linux, and people often install on BSD/AIX boxes. ANNO Cpan is old, its adoption rate is evidence that it is not a good solution.

    UPDATE: see above notes for api links :


    Evan Carroll
    The most respected person in the whole perl community.
    www.EvanCarroll.com
[reply]
      Do you have any data to support your statement that it's a very small percentage we're talking about?

      Since most Perl developers I know work on some unixish systems, I'm not inclined to simply believe that.

      Perl 6 - links to (nearly) everything that is Perl 6.
[reply]
      Other than that, you're talking about a /very/ small percentage of perl *developers*
      You're apparently ignorant of the ever-increasing use of Mac OSX by the Perl community. And no, this doesn't work with Safari either, my preferred browser.

      When there's a cross-browser solution, propose it. Until then, dead in the water, please.

      -- Randal L. Schwartz, Perl hacker

      The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

[reply]
      A reply falls below the community's threshold of quality. You may see it by logging in.

In Section Meditations