News for hackers. Stuff that matters.
Re:Peter Norvig's Sudoku solver: Clojure & Python side by side by beagle3 on Wednesday March 30, 2011 @02:17PM (#2388448)
That's so wrong it's not even funny.

You know, part of the reason Google is Google is that they were worried about performance from day 1 - every possible kind of performance.

AltaVista was king at the time. It gave low quality answers, true -- but it was also slow. All the early adopters that I know of that switched to Google were impressed more by its speed than by its quality - if you knew what you were searching for, you DID get high quality content from AltaVista at the time (much like you could with Google even before the recent "farmer" update, despite the complaints from all over). What you couldn't get from AltaVista, no matter how much you tried, was a speedy answer. AltaVista would take 5 seconds; Google would have a response in 0.05 seconds.

Unless your app is defining a new niche, you have to compete with the current players. Facebook needed to compete with MySpace. Google needed to compete with AltaVista.

Google did it by storing an index of the whole internet in Ram. That's performance you worry about from day one, not something you can add in retrospect.

Re:Peter Norvig's Sudoku solver: Clojure & Python side by side by rbanffy on Wednesday March 30, 2011 @03:01PM (#2388668)
> Google did it by storing an index of the whole internet in Ram. That's performance you worry about from day one, not something you can add in retrospect.

It really depends on implementation. I have changed many applications from RDBMS-based to file-based to memory-based when the need arose. Of course, if you intend speed to be your competitive advantage, then you need to optimize early.