Random header image... Refresh for more!

Summarizing Android

So far, my experience with Android has been brief moments of totally awesome brilliance, separated by vast swaths of WTF.

For example, why is it easier to get a speech synthesizer integrated into my application than it is to get a context menu set up?  Why is the debugger so introverted that it refuses to tell me what’s wrong?  W…h…y… …i…s… …i…t… …s…o… …s…l…o…w… …t…o… …t…y…p…e… …a…n…y…t…h…i…n…g… …i…n… …t…h…e… …e…m…u…l…a…t…o…r…?…

I understand that writing a single application meant to run on multiple different highly contstrained environments is complicated.  I understand that defining a View in XML and interacting with compiled code classes is complicated.

But Microsoft’s done it and has done it for years.  I set some things in a XAML file and it’s just there in the class.  I don’t have to use a TextBox Resource ID to look up an element I need to work with.  And I doubt they’re the first or the only that can do it.  Why can’t the flagship open source IDE figure that out?

I’m hoping that I’m just missing something.

Whatever.  At least it’s still not Objective C.

0 comments

There are no comments yet...

Kick things off by filling out the form below.

Leave a Comment