How did this work out for the class?
addisonj opened this issue · 3 comments
Apologies for the non-issue issue. It was the best way to get a hold of you :)
I am in BYU CS478 this semester and wondered how things worked out doing the class in node. Where you able to complete all the projects in node or did you run into any large problems?
Thanks for the this project and appreciate any help!
Hey! Sorry for the delay, for some reason github didn't send me a notification (that I saw until now..)
I ended up with an A in the class I think, and was able to do all the projects in node. I don't remember having any major problems, other than performance - some algorithms are just painfully slow (part of that is probably my bad implementations though!)
Hope you find this useful! Feel free to send pull requests if you find ways to improve it!
FYI, v1 of this component works just fine for large scale ARFF parsing.
We are running it through billions of ARFF files and the only major issue found was addressed in PR #4
In terms of algorithm design, this isn't 1990 and this isn't a C++ component. Just run the code through google-closure/uglifyJS as part of your NPM build and you will achieve the almost-perfect runtimes. Also realize that most browsers will optimize your code at compile time anyways. These days, it is better to make code readable/communicable than ASM-style runtime perfect.
Good work.
Great to hear this has been useful @toddpi314! I originally created it for a class in university- I never would have imagined that it would ever be used on billions of files! I'm glad it's working well for you.