NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Rough consensus and running code. (Score:2)
You know what really pisses me off? What ever happened to "hey, cool idea! A little rough around the edges, but I see where you're going." Maybe even, "here's a patch to make it better." No, I get "it doesn't do EXACTLY what I want EXACTLY the way I want it so I'm going to bloc
Re: (Score:1)
Ok, send feedback to Graham via proper channels. You don't like something? HELP FIX IT! Bitching is not doing.
I'm sorry, but when it comes to THE SINGLE MOST IMPORTANT SITE IN THE ENTIRE PERL WORLD, I like to discuss things in public. Because you know what? There's no mailing list for it. No newsgroup. No wiki. use.perl is the closest thing we have. If you, Graham or brian aren't happy with a public and gravely important community website being discussed in public, that'
Re: (Score:2)
You're in a vicious cycle. Nobody will write something different because everyone uses search.cpan.org. Everyone uses search.cpan.org because nobody has written something different. (Not to dis on kobeserach, of course, but it's also mostly the same as search.cpan.org. There's little radically different.)
But the attitude of "this is the site that everyone uses" is exactly the centralization that Schwern is talking about. Where are the CPAN mashups?
--
xoa
Re: (Score:1)
Where are the CPAN APIs?
Re: (Score:2)
--
xoa
Re:Rough consensus and running code. (Score:1)
What is that non-sequitur a reply to?
Your asked where the CPAN mashups are. I answered that the existing services provide no APIs, so no mashups get written. And no, a dump of several gigabytes worth of moderately inconsistent data in quirky formats does not an API constitute.
Reply to This
Parent