6,594 karma · joined December 29, 2014
Creator of https://hack.ernews.info/
[ my public key: https://keybase.io/antouank; my proof: https://keybase.io/antouank/sigs/MJ0DHg4TtjqT1PcdZ5Dbhf0MUk268eR62r7ovbvggaM ]
~# dd bs=1M count=1024 if=/dev/zero of=test conv=fdatasync 1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB) copied, 2.35872 s, 455 MB/s
And maybe a way to get the results would help you see differences between machines and platforms.
Node.js uses an old V8 version ( Google doesn't support it anymore, and they don't even apply security patches to it ) while io.js has the latest V8, plus all the security patches and bug fixes from the io.js codebase, that node.js does not have.
Same story with libuv, the "main" library under the hood.
( most of this explained in this podcast http://devchat.tv/js-jabber/147-jsj-io-js-with-isaac-schleut... )
If older === more stable, then I guess you should use the oldest version in everything. Makes no sense.
Check out an older intro by Zakas http://www.nczonline.net/blog/2013/07/16/introducing-eslint/
( Also I think it's a bit faster than JSHint/JSLint ).
I'm a JS engineer, worked mostly so far as a Front-end developer ( React/Flux, Angular, jQuery, knockout... ), and I'm looking for a full-stack JS project to work with.
In London or remote.
CV : http://goo.gl/vzrgrJ
latest project : http://hack.ernews.info
github: http://github.com/antouank
I already have some thoughts on how to handle the comments section, I agree it has to be very efficient cause the whole point of the client is to let you get in and out of the comments section easily. Reading the headlines is the easy part.
If anyone is a designer or has design suggestions, I'm happy to see them.
I have two stores, one for the news stories, and one for the comments. And then a smaller one for the notifications. I don't use any state in the components. Everything propagates from the top level and the stores.
The counter component doesn't have a state, but when it sees an update, it just adds/removes a class and that's how you get the animation.
I tried to reply to your comments but I was getting the "you're submitting too fast" message...
I have no problem to disable them ( optionally maybe? ) for whoever thinks they are annoying.
No need to refresh your browser anymore to see new stories and comments.
Also, I used a responsive design to be able to read the stories on my mobile phone.
For now, I only show the top stories, up to 100 of them ( that's how many the API gives you anyway ).
If people find it useful, I might add other things. Hope OAuth becomes available so I can add up-voting and comment adding.