News for hackers. Stuff that matters.
Re:Ask HN: When was the last time you used big-o in a web app? by PaulHoule on Tuesday August 02, 2011 @11:26AM (#2837444)
Web apps stick to O(N) (iterate through a list) and O(N log N) (sort, some operations on indices).

If something is O(N^2) or worse, it "doesn't scale" and you won't usually see it done in a web app. That is, there's a whole shadow universe of web apps that you've never seen because the resource demands are too high.

Re:Ask HN: When was the last time you used big-o in a web app? by bunchesofdonald on Wednesday August 03, 2011 @08:51AM (#2840917)
I disagree as well. Certainly most code that runs when you actually view a page in a web app is O(N), but there are many web apps that do backend computing that is much more complicated. Take Google and Netflix as examples.
Re:Ask HN: When was the last time you used big-o in a web app? by PaulHoule on Wednesday August 03, 2011 @05:22PM (#2843171)
You'd better believe that Google and Netflix have scientists who work hard every day trying to "bend the curve" towards O(N) in all of those applications.
Re:Ask HN: When was the last time you used big-o in a web app? by diolpah on Tuesday August 02, 2011 @12:25PM (#2837681)
Well, I strongly disagree with this. One example from our own applications would be O(m*n) for computing levenshtein distances between arbitrary product sets. Of course many of these are precomputed, but they are still used in a web application. Computing sales relationships would be another example.