21 y/o Developer from Bavaria / Germany. Working in a Web-Agency and part-time self-employed. Working with PHP (Symfony, TYPO3, Shopware), VueJS and Go.
Hey, Great Post.
Have you heard about LowDB? github.com/typicode/lowdb
It is an JSON „powered“ database, which can use the filesystem or the LocalStorage.
I don’t know how Support vor Observable objects is because I didn’t dive deep into it when I used it in the past but it was the first that flew into my mind.
Please correct me if I missed something
I hope was was able to help you
Thanks for your reply! I had a quick look at it, but assumed that it would be slower than it's alternatives, because there also just seems to be a big string getting stored. Also there hasn't been much development going on in the last couple of months.
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.
Hey, Great Post.
Have you heard about LowDB? github.com/typicode/lowdb
It is an JSON „powered“ database, which can use the filesystem or the LocalStorage.
I don’t know how Support vor Observable objects is because I didn’t dive deep into it when I used it in the past but it was the first that flew into my mind.
Please correct me if I missed something
I hope was was able to help you
Thanks for your reply! I had a quick look at it, but assumed that it would be slower than it's alternatives, because there also just seems to be a big string getting stored. Also there hasn't been much development going on in the last couple of months.
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 :)