Re: Proposal: Add new 'Matrix' object

2019-05-13 Thread guest271314
A matrix could be viewed as an array of arrays or sets or maps or other
values. How the values in the arrays or indexes are mapped is dependent
upon the requirement. The requirement could be to map the networks of this
entire planet earth; create sets of permutations; create cross word
puzzles. What is the basic functionality of the Matrix described at this
proposal?

On Mon, May 13, 2019 at 3:29 PM kai zhu  wrote:

> is that a tentative "no" as in tc39 can't easily spec some low-level
> linear-algebra primitives that would be useful for both dommatrix, and
> [gpu-accelerated] tensoflow?
>
> i do find value to industry for enhancing client-side performance of 3d
> visualization and ML.  and i'm starting to see @Ed's original question as
> whether things like this falls in the scope of javascript language-design
> (as a fundamental UX-workflow problem), or should remain an
> embedder/userland concern.
>
> -kai
>
> On Mon, May 13, 2019 at 3:34 AM David Teller  wrote:
>
>> According to the specs, DOMMatrix is limited to 4d matrices. They can be
>> used to emulate 1d-3d matrices trivially. However, many applications
>> (e.g. in graph theory) require arbitrary numbers of dimensions.
>>
>> I'm not really familiar with Tensorflow, but if I read the API
>> correctly, it seems to be limited to 1d-5d tensors. If I read the API
>> correctly, arithmetic operations are tensor operations, rather than
>> matrix operations, which have very different definitions.
>>
>> Cheers,
>>  David
>>
>> On 12/05/2019 21:31, guest271314 wrote:
>> > Neither ```DOMMatrix``` nor tensorflow functionality are exclusive to
>> > any single use case. What is the use case of the Matrix object described
>> > at this proposal?
>> ___
>> es-discuss mailing list
>> es-discuss@mozilla.org
>> https://mail.mozilla.org/listinfo/es-discuss
>>
> ___
> es-discuss mailing list
> es-discuss@mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss


Re: Proposal: native XML object support.

2019-05-13 Thread Ed Saleh
I prefer JSON over XML any time but the only area where JSON can't compete with 
XML is UI.

From: es-discuss  on behalf of Sanford Whiteman 

Sent: Tuesday, May 14, 2019 1:56:46 AM
To: es-discuss@mozilla.org
Subject: Re: Proposal: native XML object support.

> I don't think we can say that we live in a JSON centric world

But we do.

It's not that there aren't powerful XML-based applications still being
developed. And XML still buttresses some of the most important
back-end components of the modern (as well as ancient) web.

But surely you cannot have missed the fact that modern API development
has so standardized on JSON that one doesn't even need to mention the
response type anymore!

In any case, if E4X died back when we all used XML all the time, it
seems vanishingly unlikely that it would come back now… but I'm not on
TC39 so this is just my take.

—— S.

___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss


Re: Proposal: native XML object support.

2019-05-13 Thread Sanford Whiteman
> I don't think we can say that we live in a JSON centric world

But we do.

It's not that there aren't powerful XML-based applications still being
developed. And XML still buttresses some of the most important
back-end components of the modern (as well as ancient) web.

But surely you cannot have missed the fact that modern API development
has so standardized on JSON that one doesn't even need to mention the
response type anymore!

In any case, if E4X died back when we all used XML all the time, it
seems vanishingly unlikely that it would come back now… but I'm not on
TC39 so this is just my take.

—— S.

___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss


Re: Proposal: native XML object support.

2019-05-13 Thread Ed Saleh
Thanks for reply. Didn't know that it existed before!
I don't think we can say that we live in a JSON centric world when things like 
React show up and revolutionize web development. I think JSON has its uses and 
XML has its uses. UI shouldn't been ever seperated from controller since one 
can't exist without the other.

From: es-discuss  on behalf of Sanford Whiteman 

Sent: Tuesday, May 14, 2019 1:37:46 AM
To: es-discuss@mozilla.org
Subject: Re: Proposal: native XML object support.

> let foo = 

This is a retread of E4X (https://en.wikipedia.org/wiki/ECMAScript_for_XML)
so I can't imagine it would be resuscitated in a (for better or worse) 
JSON-centric
world.

—— Sandy

___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss


Re: Proposal: native XML object support.

2019-05-13 Thread Sanford Whiteman
> let foo = 

This is a retread of E4X (https://en.wikipedia.org/wiki/ECMAScript_for_XML)
so I can't imagine it would be resuscitated in a (for better or worse) 
JSON-centric
world.

—— Sandy

___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss


Proposal: native XML object support.

2019-05-13 Thread Ed Saleh
Hello,

I am proposing to support XML object native in JavaScript so the following code 
would be possible

let foo = 

Which creates an object called foo with name = "input" and value = "Ok", 
children = null, and constructor = null

`constructor` property would include a constructor to be called when a new XML 
object is created.

While `childern` would include any inner XML items inside the XML element.

It's nature to support XML as object natively next as JSON format is already 
supported natively.

Supporting XML would open new possibilities notably in the UI side as we would 
be able to merge UI with Controller logic code.

This is similar to React framework.

Thank you,

___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss


Re: Proposal: Add new 'Matrix' object

2019-05-13 Thread kai zhu
is that a tentative "no" as in tc39 can't easily spec some low-level
linear-algebra primitives that would be useful for both dommatrix, and
[gpu-accelerated] tensoflow?

i do find value to industry for enhancing client-side performance of 3d
visualization and ML.  and i'm starting to see @Ed's original question as
whether things like this falls in the scope of javascript language-design
(as a fundamental UX-workflow problem), or should remain an
embedder/userland concern.

-kai

On Mon, May 13, 2019 at 3:34 AM David Teller  wrote:

> According to the specs, DOMMatrix is limited to 4d matrices. They can be
> used to emulate 1d-3d matrices trivially. However, many applications
> (e.g. in graph theory) require arbitrary numbers of dimensions.
>
> I'm not really familiar with Tensorflow, but if I read the API
> correctly, it seems to be limited to 1d-5d tensors. If I read the API
> correctly, arithmetic operations are tensor operations, rather than
> matrix operations, which have very different definitions.
>
> Cheers,
>  David
>
> On 12/05/2019 21:31, guest271314 wrote:
> > Neither ```DOMMatrix``` nor tensorflow functionality are exclusive to
> > any single use case. What is the use case of the Matrix object described
> > at this proposal?
> ___
> es-discuss mailing list
> es-discuss@mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss


Re: Proposal: Add new 'Matrix' object

2019-05-13 Thread David Teller
According to the specs, DOMMatrix is limited to 4d matrices. They can be
used to emulate 1d-3d matrices trivially. However, many applications
(e.g. in graph theory) require arbitrary numbers of dimensions.

I'm not really familiar with Tensorflow, but if I read the API
correctly, it seems to be limited to 1d-5d tensors. If I read the API
correctly, arithmetic operations are tensor operations, rather than
matrix operations, which have very different definitions.

Cheers,
 David

On 12/05/2019 21:31, guest271314 wrote:
> Neither ```DOMMatrix``` nor tensorflow functionality are exclusive to
> any single use case. What is the use case of the Matrix object described
> at this proposal?
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss