Jacopo Scazzosi

> Which ones? @RubenVerborgh the fact that `map()`, `filter()`, `union()` `transform()`, `prepend()`, `append()` and so forth are all defined on the prototype of `AsyncIterator` means that the respective classes `MappingIterator`,...

IMHO this is a (very) good idea, although I'm unsure as to how complex the final solution might be. Could be worth having a `SequentialUnion` iterator if having everything in...

Another library to check out: https://github.com/RubenVerborgh/AsyncIterator

> I would say that http3 on roadmap is more about quic protocol and there is no straight inheritance between http3 and http2, so maybe support of http2 needs to...

@jeswr amazing work. I understand that the source-agnostic version would benefit from some form of shared dictionary encoding as per recent conversations? Also, would you be able to profile one...

@jeswr I can't seem to zoom in on that image as it's quite small in resolution but that looks like a comparison of different reasoning solutions. What I'm thinking about...

I think having a RDF/JS reasoner that doesn't depend on N3.js would be worth the 2x - 4x loss, given the absolute numbers I'm seeing. Don't get me wrong, N3.js...

I don't have time to look into this right now and therefore I apologize in advance if I end up polluting the conversation with unrelated stuff. That said, I think...

> The consequence of this is that calling engine.execute() should never cause blocking behavior, but simply return an iterator that will become readable once data is ready. I generally agree...

This is of _extreme_ interest for persistence and query optimization (pushing filters downward) as well. Quadstore has its own serialization strategy, which I bootstrapped from what used to be N3's...