HN user

eltaco

19 karma
Posts7
Comments25
View on HN

ESLint is pretty awesome - the project has a great team and always adding new functionality (cache and then parallel linting sound great)!

Although it isn't unique for all the features listed, as JSCS has the same things: an autoconfigure feature, built-in (as well as user created) presets/configs, multiple formatters, custom plugins/rules, custom parsers (esprima/espree/babel), autofixing of almost all rules. Hopefully both projects can benefit or integrate better together more in the future? (I contribute to both!)

I think autofixing for all rules (maybe with https://github.com/cst/cst) would be a nice goal for the future when thinking about the next-generation of linters. Making it easier to update configs when new rules/options are added would be nice as well.

You could try implementing some of the methods in underscore/lodash - http://underscorejs.org/? Each of those are pretty simple and can build off each other - you'll learn how to deal with arrays, objects, functions, arguments, apply/call, this, etc. You could write your own tests or use their unit tests as well to get some practice with testing. I was planning on doing this myself at some point haha.

There's an annotated source for underscore: http://underscorejs.org/docs/underscore.html.

There's also just implementing data structures/algs: https://github.com/felipernb/algorithms.js

TwitterHealth

http://i4.minus.com/ibmjeJLRAFCB0Q.png

Crowdsourcing the classification of tweets as sick related or not for my Data/Visual Analytics class. Classified tweets from users are sent to our machine learning alg.

Originally was supposed to show where and what ailments people were dealing with around the world but having only cities doesn't give that great of a visualization.

Using node, d3, cubism, redis.

App: http://twitterhealth.herokuapp.com Code: https://github.com/eltacodeldiablo/twitterhealth