Nice analogy - I'm a Captain Beefheart fan. But I beg to differ. While the Android SDK most certainly has its idosyncracies, mostly notably for me the incessant overuse of implementation inheritance and the use of ints instead of (typed) enums. It also requires a good understanding of standard design patterns and principles. Notably event handling and MVP, but many others besides. To use it as a training ground for a new developer would be asking for pain .
It would also produce a whole raft of decidedly crappy apps and examples from those who had found a way and want to tell the world, just not a good one. And the hordes would folllow. On Sep 22, 2:45 pm, Bret Foreman <[email protected]> wrote: > One of the most original musical minds of the 20th century was Don Van > Vliet aka Captain Beefheart. His music was so unusual that experienced > musicians had trouble approaching it. He preferred to find non- > musicians and train them from zero. Android is like that - it's almost > better to come at it without the expectations that an experienced > programmer would have. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
