[rcavezza]

If I were you, I'd pick a project and then cater your learning to that project. with mobile vs web apps, we're talking about completely different languages.

[misterbwong]

This. What matters most is what you want to create. When you've decided this, it almost doesn't matter what you program it in as long as you can get it done. If you're confused about which one to pick, just pick a widely adopted language that has a lot of community support and you'll have more than enough to learn with.

[throw02082011]

edit: bcrawford covered this as I was writing. It's difficult sometimes to find a path of what steps there are...so many choices.

Ok. Really stupid question time then. I understand most of what I'm working on for the mobile app.

Am I right about MySQL as a direction for what the app talks to?

I might try another project first that doesn't need outside data to get my feet wet. I may be getting ahead of myself here.

[misterbwong]

There definitely are a lot of choices-they can be paralyzing. I agree with bcrawford on this one-pick a language to do the web services portion first. Then move on to the next level of the stack. In your case this would be either the data level (MySql) or mobile app level (iPhone).

I don't know if this helps, but if I were starting from scratch today I'd choose either Ruby or Python for the web services level. They're fun, easy to learn languages that are powerful enough to get the job done.

[throw02082011]

Sounds like a good plan of attack. Thanks!