NickSeagull on master
Remove unused email (compare)
ocramz on gh-pages
Add `sampling` (compare)
ocramz on gh-pages
Add kdt, Supervised Learning se… (compare)
ocramz on gh-pages
Add arrayfire (compare)
ocramz on gh-pages
add inliterate (compare)
ocramz on gh-pages
update hvega entry (compare)
ocramz on gh-pages
Add pcg-random (compare)
My personal experience in this domain was at university studying numerical analysis and computational physics. For some dumb reason I really wanted to use C for everything at first. When I got around to anything using matrices, though, the boilerplate just killed me. I switched to octave. Sure, having a bunch of math stuff built in was useful, but what really saved me was a compact syntax built for the problem domain.
That's why I'm not sure just using raw Haskell would be the right idea.
I never got around to learning python, so I'm curious to know in what ways it was flexible enough to get heavy adoption for mathematical programming
chreekat: python is great for doing science because it runs your code no matter what. No matter what they say about pre-registering experiments, scientists just love to tinker and make up hypotheses after the fact
I must say, I've had some horrible experiments where I run Python code for hours and then finally it prints out:
Traceback (most recent call last):
File "boop.py", line 1, in <module>
print(x)
NameError: name 'x' is not defined