There are plenty of votes for a core.matrix wrapper to this great project, but I'll add one point. I came to Clojure from Common Lisp. I had a neural network application in Common Lisp that didn't use matrices, and I decided I needed to rewrite it from scratch using matrices. Common Lisp has lots of matrix libraries. However, they have different interfaces, are faster or slower in different kinds of contexts, etc. Trying to figure out which library to use would have been a lot of trouble, and if I decided to change, then I'd have to rewrite my code--or start by writing my own abstraction layer.
I didn't switch to Clojure just for core.matrix--there were other reasons that were probably more significant in my mind at the time. However, once I started using core.matrix, switching matrix implementations required a one-line change. This was very helpful. I initially assumed that clatrix would be fastest. It turned out that for my application, it wasn't fastest; vectorz was significantly faster, because my matrices are relatively small. But I don't have to worry--maybe my application will change, or there will be a new implementation available for core.matrix that's better for my application. As long as the underlying implementation supports the operations that I need, all that I'll need to change, again, is a single line of code. -- 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.
