The problem with YAML is it's a horrendously bloated spec, making it super complex to write a correct parser (unless you shim a C library). It started off as a really simple idea but then Ingy went a bit off the rails with things it could do, and the spec ended up about 10 times longer than the XML spec. Personally I don't like complex formats.
Matt. On Mon, May 28, 2012 at 12:29 PM, Vitaly Puzrin <[email protected]> wrote: > I'd like like to separate 2 questions. Your work is great, and json really > worth to be improved. For example, it's convenient, when > you need to keep things simple (for very small files), or keep speed very > fast. > > The second question, about bad yaml uptake, is ralated to lack of good > libraries for node.js. Just because project is still young. > Some libs are quite complicated, and takes a lot of time to do. But we did > pyyaml port, and you can play with it here > https://github.com/nodeca/js-yaml (there is online demo). I can bet, > that once you start use yaml, you will newer wish to return back :) > > понедельник, 28 мая 2012 г., 18:13:40 UTC+4 пользователь Aseem Kishore > написал: >> >> Great question. I actually didn't know until after I published this that >> YAML is a superset of JSON. Other than that, I didn't really consider YAML >> only because it doesn't seem to have very good uptake in JS-land. >> >> Looking at it a bit now, though, I think there might be some value in >> incremental improvements to JSON, where the syntax is still valid >> JavaScript, rather than a different and much larger syntax. >> >> Aseem >> >> On Mon, May 28, 2012 at 10:08 AM, Vitaly Puzrin wrote: >> >>> Why not to just use YAML :) ? >>> >>> понедельник, 28 мая 2012 г., 6:32:23 UTC+4 пользователь Aseem Kishore >>> написал: >>> >>>> I love JSON, but writing it by hand has always been a pain. >>>> >>>> Needing to (double-)quote keys, not being able to document the data >>>> with comments, and not having support for trailing commas or multi-line >>>> strings -- all of which are available and work perfectly well on modern ES5 >>>> engines, including Node. >>>> >>>> After stewing on this for over a year, I bit the bullet today and made >>>> this idea a reality: a "JSON5" parser that supports these and other ES5 >>>> features in JSON. >>>> >>>> https://github.com/aseemk/**json**5 <https://github.com/aseemk/json5> >>>> >>>> It's built off of Douglas Crockford's own eval()-free JSON parser, and >>>> it's available now on npm as "json5". >>>> >>>> I'd love to get your guys' thoughts and feedback on this. And it'd be a >>>> dream if package.json files could be written in this looser syntax one day. >>>> =) >>>> >>>> Cheers, >>>> Aseem >>>> >>>> -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" 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/nodejs?hl=en?hl=en > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" 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/nodejs?hl=en?hl=en
