Hacker News new | past | comments | ask | show | jobs | submit login

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.



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?


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.


It's a typo for "older".


It's just a typo. These are known to happen and predate touch screens.


> 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.


Yes, and LinkedIn was one of those databases. Hence my joke.


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.


> 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...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: