I didn't choose the name, but I agree. I'm certainly not going to do away with Text::CSV_XS since, as I said it has many users, is included e.g. in many linux distros, etc. so would cause unpredictable incoveniences to drop the name. But I agree that it would be great to combine the two and I've suggested as much to Tilly previously - we've not done it out of time constraints rather than interest. If you look at Comparison of the parsing features of CSV (and xSV) modules, you'll see that Text::CSV_XS has several parsing options that Text::xSV does not (mostly things not needed in ordinary CSV parsing but quite useful for odd legacy formats) so the two modules have other differences than the perl/C differences. I think Text::xSV::Fast might be a good idea, why don't you write it? It could simply subclass Text::CSV_XS and provide some wrappers to implement the Text::xSV interface.