Vincent Weevers

@Vaelek To be sure it's fixed in the latest version of `win-detect-browsers`, could you test it directly? Like so: ``` npm i win-detect-browsers --global win-detect-browsers --summary ```

I suggest moving browser-launcher to a new dedicated github org (or _maybe_ [`airtap`](https://github.com/airtap), which is somewhat related). It's easier to invite outside collaborators and ensure continued maintenance when there's no...

That makes `nextv()` slower because that must then "unflatten" the array in JS land. The current approach makes `nextv()` fast and `next()` only slightly slower (compared to a flattened array...

Related: are you working with binary data? If so, I've been thinking about an entirely different approach, where we allocate one buffer and slice it up in JS. But that...

@juliangruber Could you please check that the above text is not biased towards my personal preference?

If your `all()` call is a long-running operation (getting many entries) it might not be the best method to use. For that same reason, `all()` currently uses `nextv()` under the...

https://github.com/Level/abstract-level/pull/55 (as noted there, implementations have to handle the aborting, so there will be additional work here).

Help is always welcome, thank you! Though FYI, that's not why I haven't released this yet. Just haven't had the time, and I don't consider benchmarks to be a blocker...

I'm not that experienced with promises themselves, I meant more that disk and the CJS barrier are the bigger bottlenecks here. But it's always good to challenge such assumptions. You're...

A better starting point is `classic-level`. Take the minor differences between `leveldown` and `rocksdb`, and apply those to a fork of `classic-level`. That gives us a good base for maintenance,...