From: Mike Moore Date: 2007-07-25T04:19:01+09:00 Subject: Re: What libraries to be unbundled? ------=_Part_114897_18284953.1185304743403 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 7/24/07, David Flanagan wrote: > > James Edward Gray II wrote: > > On Jul 24, 2007, at 1:39 PM, David Flanagan wrote: > > > >> I don't think that json should be unbundled. It is the interchange > >> format of choice for Ajax applications, and I think it is going to see > >> more and more use. It even has its own RFC! If anything, I think that > >> json support should be migrated into the core! > > > > Ruby is a general purpose programming language. One use it gets put to > > is building Web applications. One subuse in that domain is to involve > > some AJAX. JSON is sometimes helpful in that. > > > > I'm pretty sure a "gem install json" is an OK amount of one-time hassle > > for the percentage of cases where all those conditions apply. > > > > Of course, that's just my opinion and it's obvious that the core team > > found it important enough to include. > > > > James Edward Gray II > > > > Obviously, I'm only stating my opinion about the relative importance of > JSON, too. And I think that is what NaHi was asking for. > > Your argument seems to be: > > if it is only useful for a small subset of programs, then unbundle it > > If you follow this to its logical conclusion, I think you'll end up > unbundling almost the entire standard library! Precisely! David > > > > ------=_Part_114897_18284953.1185304743403 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 7/24/07, David Flanagan <david@davidflanagan.com> wrote:
James Edward Gray II wrote:
> On Jul 24, 2007, at 1:39 PM, David Flanagan wrote:
>
>> I don't think that json should be unbundled.  It is the interchange
>> format of choice for Ajax applications, and I think it is going to see
>> more and more use. It even has its own RFC!  If anything, I think that
>> json support should be migrated into the core!
>
> Ruby is a general purpose programming language.  One use it gets put to
> is building Web applications.  One subuse in that domain is to involve
> some AJAX.  JSON is sometimes helpful in that.
>
> I'm pretty sure a "gem install json" is an OK amount of one-time hassle
> for the percentage of cases where all those conditions apply.
>
> Of course, that's just my opinion and it's obvious that the core team
> found it important enough to include.
>
> James Edward Gray II
>

Obviously, I'm only stating my opinion about the relative importance of
JSON, too. And I think that is what NaHi was asking for.

Your argument seems to be:

    if it is only useful for a small subset of programs, then unbundle it

If you follow this to its logical conclusion, I think you'll end up
unbundling almost the entire standard library!

Precisely!

   David




------=_Part_114897_18284953.1185304743403--