Vincent Weevers
Vincent Weevers
> I don't know if port to browser needed at all. Even if needed, IMHO performance is not required there and any FS backend could be ok. The problem with...
IMO we've come pretty far already with `level@5`, which ships prebuilt binaries for linux, mac, windows, arm, android, and it works in browsers. It means most of the time you...
@ralphtheninja is this about that `verb` thing?
I meant, do you plan to use the `verb` module as advertised here: https://github.com/doowb/dependents-cli/issues/5#issuecomment-327570528? (just curious)
I suggest adding: canary tests, seeking (and the things that it enables, like multi-get), manifests, fixing segfaults, benchmarks.
Updated (see edit diff).
Updated: - Added `Achieved` section - Merged `Ongoing & Future` into `Ongoing` - Added `Drop key types other than strings and buffers from memdown and level-js` - Moved benchmarks to...
> I feel having dependencies for node primitives in a meta-package such as abstract-level is overkill. What's the real reason you're asking this question? Because `abstract-level` is not a meta-package...
> I think I was trying to say that the event emitter pattern has some downsides to cleanup/deallocation. Like there is no way to remove a listener without explicity keeping...
> it breaks building this for the browser I want to add some nuance to that. Webpack, Browserify, Vite and more are perfectly capable of bundling Level modules, although some...