V8 adds support for top-level await

Re:V8 adds support for top-level await by kristiandupont on Wednesday September 25, 2019 @06:27AM (#21069367)

Operational transformations are not the "only correct" way to update an integer and it comes with a number of performance and memory/storage consumption implications.

>What modern js still has to reinvent is in-client synchronizing storage which naturally resolves who waits on what (if at all)

I don't understand what this means but it makes me curious. What would be an example of this in one of the languages that have already "reinvented" it?

[ Parent | on HN ]

Re:V8 adds support for top-level await by wruza on Wednesday September 25, 2019 @09:32AM (#21070584)

SQL.

>it comes with a number of performance and memory/storage consumption implications.

Instead of selecting sum(), CREATE TRIGGER then and update a singleton on insert. You can even create a view with N recent transactions and catch inserts into it to maintain that N, if you don’t want a full history.

[ Parent | on HN ]