Hello everybody.

I think I’ve been overlooking the people using this library and I’m sorry about that one. I think it could be much better if I had responded to you properly. Although I’ve been listening people for a long while, it’s been a scary place to give me feedback. That has changed now though.

This library has 3 dependents with documentation and 2 dependencies. I suppose it’s not a popular or widely used library, and there may be already much better libraries out there. I wonder what should we do here?

I haven’t been interested about node or udev for years, but apparently there are weird things happening. People are building statically typed languages that use Javascript as a platform, forming something similar to the link between typed-lambda calculus <–> untyped lambda calculus. I think this can be a good possible future for node/npm and whole Javascript ecosystem. The flaws are eventually resolved, and who knows if Javascript itself changes to better.

There are quite a few projects that depend on this library. Apparently one library uses it to detect mountpoints, another uses it to detect serial ports, third one uses to find usbled devices. These are clear I guess.

So let me know, what do you think should happen to this library? Is there a better library out there already? Any frustrations or issues you have had, or proposals to fix the issues?

I barely remember I made this library and I feel like it’s just a wrapper anyway. What am I even doing maintaining this? But then, there are some upcoming projects that might be relevant here. I have a C-FFI header generator that I would like to renovate. This would provide easy FFI-headers for any possible language runtime you are interested about. It might be interesting to use it in this connection, as a testbed.