Shucks.... The Spotted Pony is one of my favorite fiddle tunes. I would have (for unworthy, unprofessional reasons) love to work on a pony package.
But I think Sean has the right of it... we should just promote matrix and move the collections stuff to a collections package. On Fri, Dec 11, 2009 at 7:50 AM, Sean Owen <sro...@gmail.com> wrote: > On Fri, Dec 11, 2009 at 3:43 PM, Benson Margulies <bimargul...@gmail.com> > wrote: > > One proposal I want to make first: the token 'matrix' in the package > > names is confusing. I know you don't want to use 'colt'. How about > > 'pony' for bitvector, buffer, and functions, and 'collections' for > > list and map? A less silly alternative 'utils'. > > You're saying org.apache.mahout.*matrix* is confusing? I don't think so, > why? > Or are you referring to org.apache.mahout.matrix.*matrix*? Yeah that's > redundant, but seems the solution is to pull it all up one level? > Because the old Matrix code exists there at the moment. > > 'utils' is already in use for another purpose so I'd avoid that. > > > > I don't want to do that sort of rename in a patch. I'll start working > > in the packages as you have them for now. > > I think this sort of change is best done earlier than later. As far as > I am concerned, knock it down now. > > > > My goals are to fill in more data types in the primitive types and > > update to use generics where Objects are in flight. > > Sounds good to me. I think the more urgent change for 0.3 is doing > away with the old Matrix/Vector and switching to the new. > > Per my recent message, very glad to see someone running with this piece. > -- Ted Dunning, CTO DeepDyve
