this is at the project level (cli projects) not the platform level so I think we're ok
that said, this whole discussion reeks of bikeshed On Mon, Feb 17, 2014 at 11:17 AM, Jesse <purplecabb...@gmail.com> wrote: > FYI. Windows Phone SDK and Windows 8 'native' .net SDKs do NOT provide a > library to parse generic json objects, while reading XML is trivial. > I could easily add the 6MB JSON.net [1] library to support this, but I have > avoided every dependency I could in getting to this point, so I would > rather not. I would likely have to write ~400 LOC to use the > DataContractJsonSerializer to parse the file, which isn't a huge deal, but > should be considered. I always strive to write as little code as possible. > > Please keep in mind the 'native' implications of making the move to .json > only, and not just the convenience of inspecting, authoring, and modifying > the config file. > > > > [1] http://james.newtonking.com/json > [2] > > http://msdn.microsoft.com/en-us/library/system.runtime.serialization.json.datacontractjsonserializer(v=vs.110).aspx > > > @purplecabbage > risingj.com > > > On Mon, Feb 17, 2014 at 8:34 AM, Josh Soref <jso...@blackberry.com> wrote: > > > Jonathan wrote: > > > It fits more naturally with some 'native' tools (e.g. android & windows > > 8). > > > IDE's have better support for it. > > > > This is changing > > > http://blogs.msdn.com/b/visualstudioalm/archive/2014/02/06/json-debugger-visualizer-in-visual-studio-2013.aspx > > > > > If you're developing only with css,js,html -> json makes more sense > > > > > If you're developing using native tools (plugman flow) -> xml makes > more > > sense > > > > Tools evolve. I don't see this as a particularly strong argument. >
