Brendan Eich (2014-01-13T15:40:48.000Z)
Anne van Kesteren wrote:
> On Mon, Jan 13, 2014 at 1:13 PM, Dean Landolt<dean at deanlandolt.com>  wrote:
>> >  Value Objects. See the recent thread re: value objects on es-discuss. Slides
>> >  from the presentation Brendan linked to
>> >  (http://www.slideshare.net/BrendanEich/js-resp) confirm that == will still
>> >  be overloadable and he says he'll be working on writing it all up this
>> >  month.
>
> Value objects are immutable. URL objects do not have that quality
> which is why I titled this thread overloading for non-value objects...

Then no == for URL objects.

We want to keep the relatively few invariants in the language that we 
have. Why is it so important to have == for (mutable) URLs?

/be
domenic at domenicdenicola.com (2014-01-22T19:25:42.462Z)
Anne van Kesteren wrote:

> Value objects are immutable. URL objects do not have that quality
> which is why I titled this thread overloading for non-value objects...

Then no == for URL objects.

We want to keep the relatively few invariants in the language that we 
have. Why is it so important to have == for (mutable) URLs?