From: Jeremy R. <jr...@fa...> - 2004-09-15 17:28:44
|
Greetings. Let me beging by saying: I am no markup expert. :) I'm also quite new to YAML. I've watched the heated (!) discussions for the past few weeks in (dizzy) interest, however... and feel compelled to pipe in as a "naieve observer", insomuch as such a POV can occasionally be of use. First comment: I liked "Love Potion #9" (particualrly with the '?' in place of 'pln'... I forget the variation's name): it gives the user a little more choice than I've seen in the other options. Perhaps my feelings tied in with this comment: > I see two local maximums in YAML-space. One is > all-scalars-are-created-equal. The model is a simple as possible with > the downside that you periodically need a little extra cruft in you > files or a little more work in your application. The other is something > that's equivalent to the plain-scalar flag. Say #4 with an abstract tag. > In this case the model gets a little messier, but the files are as cruft > free as possible. All of the various compromises seem worse than these > two endpoints. ...To which my immediate feeling was "supply both". Meaning, pick one as a default and allow the other as an option, defined in the file / block header. I'm all for giving the user some added flexibility. Your gun, your foot, kind of thing. ;) Apologies if I've missed past discussion of why this is a Bad Idea. I suppose I'd just like to hear a sentence or two about why, from someone who's Been There. [Very long block of text written and removed as I talk myself through why such extensive use of symbols (as opposed to words) is wise.] Feel free to completely ignore this post as the rantings of someone who's really just trying to get his head around the spec by babbling about it. ;) |