Here are things that people either frequently or never ask me:
If your question isn't listed here or you have feedback about the app, contact me on Twitter.
If you have specific questions about how to use CodeKit, please visit the help page or watch the video tutorials. Both will get you going much faster than contacting me!
ABSOLUTELY NOT. Everything you need comes with the app and just works. Whatever language you pick, it's ready to go. And CodeKit only activates the parts that you need, as you need them, so it doesn't waste system resources.
After adding a new file to your project, you must click the refresh button in CodeKit or wait until the app auto-refreshes all projects. When you add a file, CodeKit must rescan the entire project to which that file belongs in order to check for @import links and update all files accordingly. This can take a while on large projects, so it's not done automatically every time you add a file.
Firefox has no AppleScript support, so it's currently impossible to tell that app to reload its window. Mozilla knows about the issue, but hasn't yet added proper AppleScript support. When they get around to it, Firefox will join the club.
No. I make no changes to the components that drive CodeKit (Less.js, Sass, Stylus, Uglify.js, JSLint, JSHint, Bless.js, etc). There is no difference between using these tools inside CodeKit and using them on the command line. Note: CodeKit uses the latest version of each tool as it's available on GitHub. Sometimes this is a version that's newer than the one available on the tool's actual website.
Open the about window.
A really great way to do imports and variables in HTML. See here for details.
The limit is 10,000 files. This restriction is imposed by Mac OS X itself. If your website has more than 10,000 files, you are either doing it wrong or you're Mark Zuckerburg.
I DESPISE outline views. I'll paraphrase Steve Jobs: "We'll use an outline view right? Nnnnnno. Who wants an outline view!? You gotta expand 'em and collapse 'em; yuck! So let's not use an outline view." CodeKit isn't designed to organize your file structure. Use the Finder or your editor to do that. Plus, the current setup lets me show you the output path as well as the input. You'd have to have two columns to do that with an outline view and it looks terrible. No outline views.
Apple enjoys shooting themselves in the foot.
Negative, ghostrider. CodeKit uses swanky new APIs introduced in Lion to do things faster and better. It will never run on older versions of OS X.
Tower for version control. Transmit 4 for FTP. Safari as my primary browser with no flash installed and Chrome as a fallback for flash sites. The Ghostery Plugin for Safari to keep some semblance of online privacy. Adobe CS 5.5 for designing stuff. Querious for SQL work. Reeder for RSS. MAMP to run websites locally. I love iWork and don't even have MS Office installed. I have copies of Coda, Espresso, Sublime Text 2 and Textmate; none of which I'm entirely happy with. I also use 1Password, but only because there's no alternative. I use Apple Mail and iCal, though when I'm forced to sit through the damn page-flip animation over and over in the latter app, I gleefully imagine beating some Cupertino designer with a cactus.
I use an early-2008 Core2Duo 15" Macbook Pro running at 2.5Ghz with 4GB of RAM. I have a 23" Cinema Display which I bought in 2005 and the Apple wired, aluminum keyboard (for the number pad). I have an iPhone 4 and an iPad 2 as well. I may be the only developer on the planet who actually prefers glossy screens.
The Macalope called dibs on Rob Enderle.