gicmo

RHEL kernels are heavily patched, i.e. stuff gets backported from new kernels, sometimes even from -rc if needed. The version number is therefore not that useful. Some call it a Frankenkernel. :)

I see your point and I actually agree that it probably would be better if this was either opt in, or at least have the two settings on the initial spotlight window so that you can immediately disable them without going to the settings. Also giving 'privacy' info for each spotlight 'category' is indeed a good idea.

May point about the script was more that it also just disables the two things listed in the initial privacy info given by Apple, i.e. "MENU_WEBSEARCH" and "MENU_SPOTLIGHT_SUGGESTIONS" and having informative text with screenshots to which checkboxes to unselect on the website would have sufficed. At least you wouldn't be executing code from some random place on the internet.

If you bring up the Spotlight search window it will even tell you:

"In addition to searching your Mac, Spotlight now shows suggestions from the Internet, iTunes, App Store, locations nearby, and more. To make suggestions more relevant to you, Spotlight includes your approximate location with search requests to Apple. You can change this in Preferences. Learn more…"

Clicking on "Learn more" also tells you how to disable it. The python script is neat but a bit exaggerated IMHO.

Funny, the "How can you detect a cycle in a Linked List" question is in the "Secrets of Programmer Job Interviews" Section (actually it is the Appendix) of the fabulous book "Expert C Programming: Deep C Secrets" by Peter van der Linden from 1994. Excellent read and apparently even the interview preparation section is still valid! ;-)

I am currently working in a environment, i.e. computational neuroscience lab, where getting results quickly is the most important thing and nobody really cares about the aesthetics of the code, heck not even about the resulting program (the "product") created by that programming. We therefore do indeed often write "ugly" and somewhat unclean code.

I can assure you that I have been angry about (my own and others) working but ugly code more often than not, because at some point you lose control and then you don't even understand what is going on anymore. Try making another 'quick' modification to the source base then. Oh and don't forget the fun to read some other PhD student's (scientific quick hack) code, who isn't even in the lab anymore.