On Fri, Feb 15, 2013 at 01:01:27PM +0000, Neil Bowers wrote: > It'll be a fun challenge, but to be honest I don't want to invest a bunch of > time into this if it's not going to go anywhere: I was after either a bit of > discussion, which naturally might point out why this is a non-starter, or > something along the lines of "fair enough, if nothing comes out of the > woodwork, if you can provide a working solution to this, we'll go for it".
The thing is, the basic questions are: (1) Will this make things better? (2) Will we get sufficiently screwed by edge cases to make it not worth it? I think the answer to (1) is a qualified yes, in that you've already demonstrated that there are problems that would be solved by such a chance. But I don't think there's any way to get an answer to (2) other than trying to provide a working solution and seeing how sharp the edges turn out to be. So, I think my personal opinion is "if you can provide a working solution, I would in theory be in favour of it, but theory and practice are not always the same so you need to prove that it works in practice too". > But I'll start getting my head around the PAUSE internals anyway. Good man :) -- Matt S Trout - Shadowcat Systems - Perl consulting with a commit bit and a clue http://shadowcat.co.uk/blog/matt-s-trout/ http://twitter.com/shadowcat_mst/ Email me now on mst (at) shadowcat.co.uk and let's chat about how our Catalyst commercial support, training and consultancy packages could help your team.
