Anyone who really chafes with the UI model of OS X probably wouldn't apply to work in Software at Apple, and even if one did you'd probably get rejected for oth

Anyone who really chafes with the UI model of OS X probably wouldn't apply to work in Software at Apple, and even if one did you'd probably get rejected for other reasons. If you're chafing on command-tab, try hitting its complement command-backtick As for tools, you can use whatever you think is best for the job, it's just that for anything that touches the GUI the best tool is going to be Obj-C/Cocoa. In other places, the HN mindset comes out to play pretty hardcore: The process sandboxing engine introduced in 10.5 is an embedded LISP Their CalDAV and Wiki Server implementations are in Python with Twisted They once shipped a desktop app written in Rails. Really. The iTMS backend is all Java, and at least formerly used WebObjects heavily For a while they had a bunch of GUI Java apps written with their Java/Cocoa bridge They've let motivated employees write Obj-C bridges for Perl, Python, and Ruby (x2) The guy that wrote two Ruby bridges is now doing a native Ruby implementation They've got at least 3 independent javascript frameworks shipping with webapps