3 ms·
but if the underlying primitives in the problem are vectors/matrices, then it seems like you are reinventing the wheel in a very substandard way that doesn't ai
by kick 7y ago
but if the underlying primitives in the problem are vectors/matrices, then it seems like you are reinventing the wheel in a very substandard way that doesn't aid in understanding in any way and results in something that isn't beautiful, isn't high performance, and is confusing for someone to read
You mean like...both of the languages you listed?
There's an obviously superior, faster, simpler language when working with vectors (APL), but people are obsessed with new languages.
If you really think it can be done in Python better than in Haskell, why not demo it in Python? You'll get internet points, and if you're right, you'll have something to show for it.
- stfwn 7y ago> Why not demo it in Python? Not OP, but here: https://gist.github.com/stfwn/62e51d86ca4ff155becd3c6a14adf60e https://gist.github.com/stfwn/62e51d86ca4ff155becd3c6a14adf6... You should be able to wget the file and run it (Python 3) from start to finish without any set-up and get ~88% accuracy on the test set. It uses all the data (not one-sixth like in the blog posts) and does 200 iterations by default, so here's the loss plot on the training set if you want to skip all the fun: https://i.imgur.com/F57zmXV.png https://i.imgur.com/F57zmXV.png