The dependency issue is important to my mind. This solution seems like a gray compromise
Sent from my iPhone Michael McGrady Principal investigator AF081_028 SBIR Chief Architect Topia Technology, Inc Work 1.253.572.9712 Cel 1.253.720.3365 On Dec 26, 2010, at 4:40 AM, Niclas Hedhman <nic...@hedhman.org> wrote: > On Thu, Dec 23, 2010 at 6:11 AM, Sim IJskes - QCG <s...@qcg.nl> wrote: > >> Could we use xml? XML based processing is already in the java rt and it >> saves us another dependency. If things need to be tooled in a later stage i >> would prefer xml. To be honest, coding in DOM will cause me to tear at least >> a few hairs out, and JDOM is my favorite (which will cause another >> dependency). >> >> To be honest, my preference for XML is a purely emotional one. > > Short list; > JSON pros over XML; > * Most of the time less verbose > * Parsing much faster and less resource intensive > > XML pros over XML > * Namespaces > > In my current main project (Qi4j) we rely quite heavily on JSON, and > at the same time we want as few dependencies as possible. Solution; > Copy-Paste an implementation into our sources. It isn't rocket science > to get JSON right. > > > That said; I leave it to you guys to work what you want. > > > Cheers > -- > Niclas Hedhman, Software Developer > http://www.qi4j.org - New Energy for Java > > I live here; http://tinyurl.com/3xugrbk > I work here; http://tinyurl.com/24svnvk > I relax here; http://tinyurl.com/2cgsug
