Definitely guys -- thanks for the feedback and for the discussion.
Chicken-and-egg problems are always hard. As an attempt to make JSON5 more
feasible, I've purposefully made stringify() output regular (strict) JSON.
So existing tools could continue to write regular JSON; it's just my hope
that for cases where JSON needs to be written or edited by hand, tools be
flexible in reading JSON.
And yes, I thought a great guiding principle was to continue to be valid JS.
Aseem
On Mon, May 28, 2012 at 10:26 AM, Angel Java Lopez <ajlopez2...@gmail.com>wrote:
> Well, I see a value: compatibility with eval.
>
> That should be the key for this project: it's not "another markup
> language". It's plain Javascript (wo/need eval)
>
> Initially, I had the idea to suggest:
>
> {
> mypage = 'loret
> ipsum...
> ...
> ....'
> }
>
> that is, multiline string, where the end of line (without \ at end) were
> preserved when loaded. But then I realized that feature would break eval
> semantic
>
>
> On Mon, May 28, 2012 at 11:19 AM, Nuno Job <nunojobpi...@gmail.com> wrote:
>
>> While I appreciate your work I would like to ask if you think the
>> advantages of these additions are enough to justify:
>>
>> 1) The added complexity
>> 2) Changing the semantics of something already completely defined and
>> with a very large tools ecosystems around it.
>>
>> In other words, markups are cool but maybe this is not JSON? :) Funny
>> that someone said it might be YAML (yet another markup language) :)
>>
>> Anyway, kudos on great OSS work!
>>
>> Nuno
>>
>>
>> On Mon, May 28, 2012 at 3:13 PM, Aseem Kishore
>> <aseem.kish...@gmail.com>wrote:
>>
>>> 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 <vit...@rcdesign.ru>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/**json5 <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 nodejs@googlegroups.com
>>>> To unsubscribe from this group, send email to
>>>> nodejs+unsubscr...@googlegroups.com
>>>> 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 nodejs@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> nodejs+unsubscr...@googlegroups.com
>>> 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 nodejs@googlegroups.com
>> To unsubscribe from this group, send email to
>> nodejs+unsubscr...@googlegroups.com
>> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
