Hi Mike, On Monday, June 22, 2015 at 1:56:46 PM UTC+2, Mikera wrote: > > Hi Dragan, > > The situation as I see it: > - You've created a matrix library that performs well on one benchmark > (dense matrix multiplication). > It performs well on all benchmarks, even BLAS 1 vector stuff is faster than primitive arrays and vectorz for anything but the very small vectors. I just didn't publish all that benchmarks that I've been doing continuously because dgemm is what is most telling.
> - Neanderthal meets your own personal use cases. Great job! > - Neanderthal *doesn't* fit the use cases of many others (e.g. some need a > portable pure JVM implementation, so Neanderthal is immediately out) > - Fortunately, in the Clojure world we have a unique way for such > libraries to interoperate smoothly with a common API (core.matrix) > And I've already made it clear that I am happy about that. Please do continue to use what works for your needs. > - Neanderthal could fit nicely in this ecosystem (possibly it could even > replace Clatrix, which as you note hasn't really been maintained for a > while...) > - For some strange reason, it *appears to me* that you don't want to > collaborate. If I perceive wrongly, then I apologise. > I would like to collaborate. I would like to offer help to anyone who needs core.matrix integration and wants to build it and maintain it. I do not have time, resources, knowledge, and need to do that work myself. > If you want to work together with the rest of the community, that's great. > I'm personally happy to help you make Neanderthal into a great matrix > implementation that works well with core.matrix. I'm 100% sure that is an > relatively simple and achievable goal, having done it already with > vectorz-clj > Thank you for the willingness to help me do that work, and I will definitely ask for it if/when I need to do that. I hope someone who might need that integration would step in and do the work, and we could both help him with that. > If on the other hand your intention is to go your own way and build > something that is totally independent and incompatible, that is of course > your right but I think that's a really bad idea and would be detrimental to > the community as a whole. > Sorry, but I fail to see how something that is open and free and solves the problems of some but not all potential users can be detrimental, but I respect your opinion. > Fragmentation is a likely result. At worst, you'll be stuck maintaining a > library with virtually no users (the Clojure community is fairly small > anyway... and it is pretty lonely to be a minority within a minority) > What you see as fragmentation I see as open choice. Neanderthal can not have virtually no users, when there is *at least one happy user* - myself, which is, incidentally, the one most important user for me. It is not like I am a salesman hustling for money. I created a library to satisfy my needs that were unsatisfied by the existing offerings, and I released that library for anyone for free. If anyone feels it's not right for them, they can step in and adapt it or use something else. That's how open source works. > > I can see from your comments below that you still don't understand > core.matrix. I'd be happy to help clarify if you are seriously interested > in being part of the ecosystem. > Yes, apparently I don't understand it. And this may be a major point in all this discussion. If I, a pretty informed and experienced user, am not understanding an API that aspires to be THE api for a domain that has not been unified in any language on any platform yet, how are casual users going to understand it? I would like the clarification, not only for me, but for all people that might need it in the future. > Ultimately I think you have some talent, you have obviously put in a > decent amount of work and Neanderthal could be a great library *if and only > if* it works well with the rest of the ecosystem and you are personally > willing to collaborate. > > Your call. > I am willing to help, and to contribute, and all that, but how to RTFM when THERE IS NO TFM to read? The call should be on core.matrix people to explain the idea clearly and to document the whole stuff, so anyone who is interested could try to understand it and see whether he/she is able to help. Current state of documentation is far from useful, and only people who designed it can do something about that. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
