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

No, other people have pointed this out, this should have been very easy to recognize as inefficient in the source code. More likely the code was written hastily and only tested against very small inputs, and then nobody ever actually tried to improve the famously long load times.


The sscanf issue was not obvious: it looks linear. And should be, on a better sscanf implementation.

The duplicate checking on the other hand is a classic "accidentally quadratic" case that is obvious.




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

Search: