Hello, first post here.
I would like to express my concerns for the direction of the Node client.
I have worked on a large number of node libraries and I believe that public modules should be made using the highest standards and implement the best practices of the industry.
This is a small list of changes that can greatly increase the trust level of Node developers towards Aerospike.
Give the JS part some love.
Follow the industry guidelines.
Avoid printing directly in the console. This applies to any library. You don’t want your console polluted by logs you didn’t ask for while running your app. There are GREAT tools available on NPM to solve just that. (I opened an issue : https://github.com/aerospike/aerospike-client-nodejs/issues/82)
Don’t bundle benchmarks, docs and examples.
Benchmarks and examples should be put in a different project, and documentation too. We don’t need those when requiring the library, say in production. It’s about 350kb of stuff we have to download. Check how Waterline does it : https://github.com/balderdashy/waterline-docs
More feedback from collaborators
It would be my pleasure to work on some of those requests. Yet, I get no replies or acknowledgement to my issues or merge requests. A big part of choosing a technology to work with is the amount of support, the solving rate for issues and finally : community involvement. There are currently a lot of unattended issues and merge requests. You will lose the interest/respect of the community and fall behind if you don’t follow up on community requests. It would also be very interesting to have visibility on the roadmap and currently assigned tasks/bugs.