4 ms·

Meh, this post was pretty unsatisfying. Should anyone be shocked that you shouldn't do synchronous calls in an asynchronous framework? Or that you should use

Meh, this post was pretty unsatisfying. Should anyone be shocked that you shouldn't do synchronous calls in an asynchronous framework? Or that you should use nginx to serve your static content and not Node? Requesting remote services in parallel is a no brainer. What does blazing fast really mean here? Using your framework correctly just sounds like "normal fast".

SiVal 14y ago
A good checklist of important items for optimizing performance should list the important items. That's what she did. Each reader can then skip over the items he already knows. It wouldn't be a better checklist if it left out important items on the grounds that some readers might already know some of them.
- 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 ago
    What 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 ago
      It's a typo for "older".
    - sausagefeet 14y ago
      It'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 ago
      Yes, and LinkedIn was one of those databases. Hence my joke.
  - dclaysmith 14y ago
    Node 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...

SiVal 14y ago

A good checklist of important items for optimizing performance should list the important items. That's what she did. Each reader can then skip over the items he already knows. It wouldn't be a better checklist if it left out important items on the grounds that some readers might already know some of them.

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 ago
  What 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 ago
    It's a typo for "older".
  - sausagefeet 14y ago
    It'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 ago
    Yes, and LinkedIn was one of those databases. Hence my joke.
- dclaysmith 14y ago
  Node 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...