Great idea, and so very obvious in hindsight.

I wish them luck. No, really.

The pragmatic call is, wait until you need to scale, if at all.

This. It's less about scaling a framework, than it is about scaling your particular application.

If you find that MySQL is a bottleneck in particular, Ruby (and by extension Rails) has a wide range of database adapters and database ORM's available. Active Record itself has numerous adapters, which mean changing databases within the supported set shouldn't be too difficult.

Alternatively, you could use a different ORM such as DataMapper or one specific to the database you desire. Rails now let's you choose which ORM you wish to use, although if you're just getting started it might prove an additional learning curve as most of the documentation uses Active Record.

Totally iOS. (1) Non-trivial Android development is much more difficult due to fragmentation and random bugs, (2) in AppStore, your chances of at least breaking even are way higher than in Google Play.

> CPU Quad-core 1.4 GHz Cortex-A9 > GPU Mali-400MP

Finally, smooth animations?

I've been getting smooth animations on my Nexus S ever since I put ICS on it a few months back and this phone "only" has a 1 GHz single core CPU and 512 MB of RAM.

Mostly metal and/or japanese otokei doujin (like IOSYS).

And yes, listening to the same thing puts me in likely the same mood.

I totally disagree with your peers, Django is very well suited for larger apps.

As for guides, I cannot recommend something specific. Take a look at the docs, they had nice tutorial last time I checked.

Google Dart, it better be.

cl.ly

Magic!