Beefy Boxes and Bandwidth Generously Provided by pair Networks
go ahead... be a heretic
 
PerlMonks  

Re^3: Can I please have *simple* modules?

by brian_d_foy (Abbot)
on Nov 23, 2005 at 07:45 UTC ( #511023=note: print w/replies, xml ) Need Help??


in reply to Re^2: Can I please have *simple* modules?
in thread Can I please have *simple* modules?

As a consumer, it's already hell. You'd be adding a grain of sand to a beach. :)

The only way to get rid of the bad interfaces and unmaintained modules is to upload good interfaces that somebody will maintain. That the space is cluttered with crap shouldn't keep out the good stuff. Once you upload, I can say "Don't worry about remembering the name, just use the one Ovid wrote." :)

--
brian d foy <brian@stonehenge.com>
Subscribe to The Perl Review
  • Comment on Re^3: Can I please have *simple* modules?

Replies are listed 'Best First'.
Re^4: Can I please have *simple* modules?
by Mutant (Priest) on Nov 23, 2005 at 10:28 UTC
    I agree, the pollution isn't really an issue at this stage. I don't really bother browsing CPAN at all. If I need a module for a specific task, I simply ask other people for recommendations. The cream does rise to the top; a good example is with date modules. A couple of years ago, there was a huge slew of them, all with various pros and cons, and most with some issues. Now, I wouldn't really think of using or recommending anything other than DateTime - it's the DBI of date modules.

    If there are major issues with existing modules, then I don't think people can complain if you release another one. Especially if you can't get the existing modules patched, and you put a note in the POD saying something like "Why another XXXX module?" and clearly lay out your reasons for re-inventing the wheel.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://511023]
help
Chatterbox?
[Corion]: ambrus: Hmmm. It makes sense that AnyEvent would implement the push_write itself, but I think I don't have a good idea of where the boundary between AnyEvent and the underlying event system lies... Implementing the timer should give me a better idea
[ambrus]: Corion: push_write is in the higher level abstraction of AnyEvent::Handle, not in the watcher
[Corion]: ambrus: Hmm - rereading Prima::File, that merrily coincides with what Prima does - it tells you "you can read", and you're supposed to read from the fh yourself. I thought it called you with the data already read, which would've been harder to integrate
[ambrus]: you just need an io watcher, created by &AnyEvent::Impl:: Whatever::io(...)
[Corion]: So after talking it through with you even while I'm still not entirely clear on where AE ends and my implementation begins, I think I understand that I only need to implement some smaller parts for each functionality I want to support.
[Corion]: Yeah... and you might even be able to mix and match additional functionality if you have additional async suppliers, like from a separate thread
[ambrus]: You hvae to be careful with the timer, because apparently Prima::Timer insists on being periodic, wheras AnyEvent::Impl:: Whatever::timer should give a one-shot timer watcher

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (6)
As of 2016-12-08 12:23 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    On a regular basis, I'm most likely to spy upon:













    Results (141 votes). Check out past polls.