Poll: what to do with streams?

[vweevers]

In a world without levelup (#58), what would you like to do with streams?

Edit: poll is closed (2021-12-10).

Option	Votes
Remove in favor of for await...of db.iterator()	5
Move to module: streams(db); db.createReadStream()	3
Move to module: createReadStream(db)	2
Use level-iterator-stream: stream(db.iterator())	1
Add to abstract-leveldown (temporarily to ease migration)	1
Add to abstract-leveldown (using streamx)	1
Add to abstract-leveldown	0

[MeirionHughes]

Personally, I've been favouring WebAPI Streams. So I've already been wrapping iterators with my own code to make them API ReadableStream. Given the examples above, mine would be comparable to createReadStream(db, opts).

If I'm pragmatic - adding it to abstract-leveldown is the path of least resistance and least breaking changes, while achieving your goal of getting rid of levelup.

[juliangruber]

I'd like to propose an option that isn't on this list: use async iteration, on iterators

[vweevers]

@juliangruber What do you mean by async iteration, if not for await...of? That's the last option on the list, and supported today.

[juliangruber]

Ah, I thought the last option was for async iteration on db.create* methods, I meant for await ... of db.iterator() yeah!

[vweevers]

Edited to clarify that.

[vweevers]

I closed the poll. Thanks for voting! Most folks are in favor of removing streams. Some folks still want to use them, so I will write a standalone module (tracked in Level/abstract-level#2 until it has its own repo) and an upgrade guide for folks that will be migrating from a levelup db.

[vweevers]

To follow up: you can now choose between for await...of and Node.js streams and Web Streams.