Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>I think the point is that he didn't know there was a lock.

One could argue that if you decide to go concurrent for performance reasons it's your responsibility to check for implicit locking behavior. Otherwise you're just doing cargo cult programming.



That is the point of the article. Explaining what you should be doing is the purpose of any tutorial-style article.




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

Search: