Agreed, and for many applications, I prefer JSON. If I'd designed XML, it would have been a lot simpler.
Still, using JSON for this would need some naming convention to avoid name collisions. A big advantage that XML has is that there are a lot more tools available for XML than for JSON. So you can pretty much be sure that almost anything you do, you'll have to deal with some subset of the XML standards, in all their glory. So you've got to do it. But the upside is, what you learn will come in handy on the next 1024 projects or tools you come in contact with... But no question, it's a major investment of time. On Mar 8, 1:53 pm, Greg Donald <[email protected]> wrote: > On Mon, Mar 8, 2010 at 3:41 PM, Yahel <[email protected]> wrote: > > like an xml file being 20% filled with > > "android", I have trouble not thinking there was a better way. > > You're not alone. I often think about JSON and Yaml and their much > smaller syntax.. unfortunately it seems Java + XML is here to stay. -- 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
