> • dependencies > > I still think that DBI should be XS, and people should really try > very very hard to make that work. Pure-perl DBI won't fly. Modules > and applications that are now depending on DBI do not want to be > depending on an extra layer, however thin it might be.
Ah yes, I think we can easily agree that there should not be an extra layer. Just a proper selection mechanism that imports the best available module at compile time. As it is right now, PurePerl DBI is very hard to use because it doesn't install, except in cases where XS works (and PurePerl is thus pointless). (Okay, "pointless" is exagerrating, of course. There are other use cases for PurePerl than getting around C compilation. Just making a point..) > • speed > > DBI was (and still is) written to get the last nanosecond out of > your database connection. Any slowdown will not be appreciated by > the current user-base. Agreed, there should be absolutely no slowdown. > DBI is Tim's product, but getting more and more a community effort. > I bet he'd love your work on getting DBI::PurePerl working [...] Tim, what say ye?
