Jake Archibald
Jake Archibald
> browsers will schedule workers with the assumption that they are CPU bound A lot of early worker demos used sync XHR, so I guess workers were invented with non-CPU...
The mmap discussion was making me feel the same way. I guess I went too high-level.
Makes sense. I wonder if `.copy()` would offer any perf benefit. We might be able to be smart about streams and get the same benefit. `.copy()` might still be nice...
mmap discussion happening in https://github.com/jakearchibald/byte-storage/issues/4, so this is more about other kinds of seeking, if needed.
You could put metadata in headers, but it could be that indexeddb is a better fit.
I really like this as a way of 'fixing' the IDB API without breaking compatibility. I think the return of `transaction()` can remain the same, but add a `.complete` promise...
I'm happy with async iterables here. I take it advance/delete and break statements all do the right thing here?
Strongly agree with having `upgrade` as part of the options object - much easier to reason-about as they say.
I've split out the reindenting commit. The actual changes are at https://github.com/atotic/event-loop/pull/3/commits/9427d9b3f929d96aa9ca58e0d8031b7fdd3abf4f
TIL about ?w=1! However, I split out the commits, so you can also see https://github.com/atotic/event-loop/commit/9427d9b3f929d96aa9ca58e0d8031b7fdd3abf4f.