[xyclos]

I will generally ask candidates a few questions about every skill on the resume. So, if you're not comfortable answering a few general questions or having a meaningful conversation about the skill then you should not include it on your resume. Including a skill level can help frame the conversation or give context, but if you can't provide 2-5 minutes on the pros and cons of the language/skill, then I'll assume you don't actually possess that skill.

[jjjjjjjjjjjjji]

I've been doing iOS development for 2 years. As an employee around 9 months, freelancing over a year and so on.

If someone asked me what is some pros and cons about Objective-C I really don't know what to answer.

I am not really fuzzed about language details, if someone gives me python - I will use it, perl - sure, bash? why not, c++ - sounds like fun and so on. I just don't care, if the language can solve the problem, then I can figure out how to use it for the problem at hand.

Sure some languages can obviously do tasks faster/better because of language details - for example I used Python recently because it was easier to write a script to handle some files, usually I'd use bash scripting.

I've been programming for years and years and I can solve most problems that are thrown at me, no complaints from co-workers or anything like that.

How should I deal with this "interview" question? Just read books? I never got these arguments online where people feel so strongly about whatever language X or Y.

[dktbs]

I assume (perhaps wrongly) that the interviewer is less interested in your opinions of the language and more interested in your ability to talk competently about the language for a few minutes.

[xyclos]

this exactly.