Agoric / ECMA TC39, TC53 presentations

This is a recorded reprise of the presentation Kris Kowal gave at ECMA TC39 on July 19, 2022, revealing a new layering of the Compartments proposal (stage 1) that aligns each of those layers with different motivating cases and provides a coherent framework for module proposals going forward.

No description provided.

No description provided.

No description provided.

Original plan was to go for stage 1 at Dec 2019 meeting. But not enough time for full presentation.

No description provided.

No description provided.

Presented at TC39 Oct 2019. https://github.com/tc39/proposal-eventual-send
Achieved stage 1 status.
Slides:
https://github.com/tc39/agendas/blob/master/2019/10.eventual-send-as-recorded.pdf

This proposal adds eventual-send operations to JavaScript Promises, to express invocation of operations on potentially remote objects. We introduce the notion of a handled Promise, whose handler can provide alternate eventual-send behavior. These mechanisms, together with weak references, enable the creation of remote object communications systems with promise pipelining. This proposal is not specific to any one remote object system. Instead, it specifies a general mechanism for hooking in whatever host-provided remote communications facilities are at hand, without constraining the nature of those facilities.

Presented at TC39 Oct 2019. https://github.com/tc39/proposal-oom-fails-fast
Achieved stage 1 status.
Slides:
https://github.com/tc39/agendas/blob/master/2019/10.oom-fails-fast-as-recorded.pdf

The ECMAScript specification nowhere mentions the possibility of running out of memory (OOM), and so cannot be correctly implemented on finite memory machines. Allocation in JavaScript is pervasive and implicit, implying that an OOM may happen anywhere in the execution of the program. If OOM threw a catchable error, computation within the agent would continue in an inconsistent state. Instead, we should immediately terminate the agent cluster, in order to abandon all unrepairable inconsistent state.

Presented at TC39 Oct 2019. https://github.com/tc39/proposal-readonly-collections
Achieved stage 1 status.
Slides:
https://github.com/tc39/agendas/blob/master/2019/10.readonly-collections-as-recorded.pdf

Currently, JavaScript collections are unconditionally mutable. We believe many use cases could benefit from separating the ability to query a collection from the ability to mutate it. We’ve seen repeated calls for such support. To minimize the cognitive load of new API, we propose the addition of only three new methods to all collections and the addition of new collection classes whose APIs are only a subset of the existing collection abstractions.

Presented at TC39 Oct 2019. https://github.com/tc39/proposal-wavy-dot
Achieved stage 1 status.
Slides: https://github.com/tc39/agendas/blob/master/2019/10.eventual-op-as-recorded.pdf

This proposal is to investigate notational support for promise pipelining. The concrete syntax we’re starting with is the “~.”, chosen by analogy with the optional chaining operator “?.”. Both can be thought of as “_adjective_ dot”, i.e., like dot but different somehow. For ~. The difference is that the operation is performed eventually and possibly remotely.

The "SES Status Update" presentation I originally gave at the July 2019 tc39 meeting I gave again to the SES-mtg on Aug 1, and recorded.

"SES Status Update" as originally presented at tc39 at
https://www.youtube.com/watch?v=cspzkRvs1Ig
Starts at the fourth slide because I forgot to turn recording on earlier.

Full Aug1 SES mtg at
https://www.youtube.com/watch?v=IxwX200g4TI&list=PLzDw4TTug5O1jzKodRDp3qec8zl88oxGd

No description provided.

As given to tc39 meeting July 2018

Vision talk at July 2017 TC39 Meeting

Watch this or https://www.youtube.com/edit?o=U&video_id=YQFPAyCgOlI

In this one you can hear the questions and see the speaker. The other has sharper images and smoother animation.