5 ms·
Well, she failed to mention "make sure computer is plugged in". Please, it's 2012, if you are using an asynchronous framework, doing things asynchronously shou
by sausagefeet 14y ago
Well, she failed to mention "make sure computer is plugged in". Please, it's 2012, if you are using an asynchronous framework, doing things asynchronously should hardly be a surprise. And serving static content via a CDN or Nginx has knowledge order than dirt. This information would be fine if I was reading a college students blog, but this is LinkedIn, I expect something a little bit more. Maybe the next blog post will be on how to store salted passwords?
- 18pfsmt 14y agoWhat does, "knowledge order than dirt" mean, exactly? Are these types of errors a symptom of touch screen input, or apathy? I have noticed the occurrence has increased greatly over the last few months. I feel like a pedantic asshole, but it greatly impairs my ability to read comments fast, and it gives me the impression that code written by the same people would confuse me as a beginner/ hobbyist.
- j2labs 14y agoIt's a typo for "older".
- sausagefeet 14y agoIt's just a typo. These are known to happen and predate touch screens.
- dbaupp 14y ago> Maybe the next blog post will be on how to store salted passwords? Given the number of hacked password databases that weren't hashed and salted, this might actually be useful.
- sausagefeet 14y agoYes, and LinkedIn was one of those databases. Hence my joke.
- dclaysmith 14y agoNode is currently v0.6.19--it's in it's infancy and people will find some of this information useful. If you don't find it useful, don't upvote it. Comment if you disagree with her points. For what it's worth I'm working on a project that uses Node.js and took something away from this article.
- sausagefeet 14y ago> If you don't find it useful, don't upvote it I didn't > Comment if you disagree with her points That would be what you're replying to now...