On Wed, Sep 11, 2013 at 03:17:22PM -0400, Jonathan M Davis wrote: > On Wednesday, September 11, 2013 11:04:37 H. S. Teoh wrote: > > On Wed, Sep 11, 2013 at 01:24:38PM -0400, Jonathan M Davis wrote: > > > On Wednesday, September 11, 2013 16:11:10 John Colvin wrote: > > > > Why not YAML? It's cleaner than JSON and is very widely known. > > > > > > YAML is just plain evil. It doesn't ignore whitespace. > > > > [...] > > > > It's funny. I used to think Python is evil for the same reason, > > Well, I hate that about python too, but what I _really_ hate about > python is that it's dynamic. It shouldn't be possible to do things > like change the type of a variable based on whether an if condition > was true or not (or change the type of a variable at all for that > matter).
Yeah, this is something oft touted as being 'convenient' and 'easy', but then in production code, you find yourself writing type checks anyway just to make sure what's passed in is what you expect. (And things blow up in horrible ways when some stray code passes in something with the wrong type.) Which defeats the purpose of having a dynamic language in the first place. > I use python at work when I need to use a scripting language, because > it's the best option that I have there, but otherwise, I'd just use D. Well, that's why we're here, right? :) If I were fully happy with Python, or whatever else it is out there, I wouldn't be here in the first place. > > But I've never used YAML, so I can't say whether or not I'd like it. > > JSON is a subset of YAML 1.2, so they're very similar. Probably the > most obvious differences are that you don't need as many quotes in > YAML, and whitespace matters. I've had to deal with it some at work, > and I hope to never have to deal with it elsewhere. [...] Wait, how can JSON be a subset of YAML if whitespace in YAML is significant, but it isn't in JSON? T -- Almost all proofs have bugs, but almost all theorems are true. -- Paul Pedersen
