It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
The case for LowDB looks to be "you're already bundling lodash into the frontend and need to do a little something stateful" which of course is not universally applicable. But that aside, disqualifying it on the grounds of a few months of inactivity isn't really reasonable -- some libraries are just mature, even in JavaScript.
You're right about that. It wasn't the main reason not use it. But I also would argue that it can be a sign that the maintainer has no or at least less interest in it. Other people might be better adjusted but I personally tend to 'improve' the software I care for even if I shouldn't :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The case for LowDB looks to be "you're already bundling lodash into the frontend and need to do a little something stateful" which of course is not universally applicable. But that aside, disqualifying it on the grounds of a few months of inactivity isn't really reasonable -- some libraries are just mature, even in JavaScript.
You're right about that. It wasn't the main reason not use it. But I also would argue that it can be a sign that the maintainer has no or at least less interest in it. Other people might be better adjusted but I personally tend to 'improve' the software I care for even if I shouldn't :)