I took a look at the tool and… it’s interesting but I can’t think of a good use case for it.
The fact that it’s ephemeral (unless explicitly saved), makes me believe I could use it as a cache… but then there are better tools for that. The fact that it exposes crud endpoints for whatever entity you set is interesting… but unless this lives in a completely trusted environment and I’m trying to hack together a personal tool… I’m going to need to build a security layer. Otherwise any user of my site will be able to modify all of the data in the datastore. If I wrap this in an API of some sort, I’ve lost the main benefit of having those crud endpoints
Probably great for some use case, but I’m struggling to see how I could use it.
At that point I could probably use local storage, unless the throwaway project I’m building absolutely needs multiple users on different browsers. It’ll mostly be throwaway code if I’m leveraging local storage or this api, but I could run local storage entirely in the browser without messing with another thing I need to make sure is running.
So, if I need a multi user site and I want put together a hack to show some possibility, then sure. I think in that case I would probably just build some cheap nodejs apis into whatever dev server I’m using. The code would be less throwaway at that point.
Either way, good on you for building this out. It’s a cool concept and even if it’s a niche situation, maybe it’ll make someone’s life a little nicer. If you had pitched this use case, then it would have been fine and maybe informative. (And I would have never complained)
Using browser local storage is actually less work in my opinion. For the other options, it’s a bit more work but not that much and the end result would be a lot more usable. (Especially with all the QuickStart options now)
My main problem is that business logic Id want to code into the backend would now be coded in the front end. Unless I’m going to throwaway all of this code, that’s going to be significantly more work to unwind. If I’m throwing it away, don’t care about security, and need to support multiple computers connecting then this is a good niche product for me.
There’s nothing wrong with it being designed for this niche. Also, I’m just giving you feedback because you asked for it
I took a look at the tool and… it’s interesting but I can’t think of a good use case for it.
The fact that it’s ephemeral (unless explicitly saved), makes me believe I could use it as a cache… but then there are better tools for that. The fact that it exposes crud endpoints for whatever entity you set is interesting… but unless this lives in a completely trusted environment and I’m trying to hack together a personal tool… I’m going to need to build a security layer. Otherwise any user of my site will be able to modify all of the data in the datastore. If I wrap this in an API of some sort, I’ve lost the main benefit of having those crud endpoints
Probably great for some use case, but I’m struggling to see how I could use it.
It’s for front end developers who need a instant API, so that they can hack some project to be shown on the next day or or next hour.
At that point I could probably use local storage, unless the throwaway project I’m building absolutely needs multiple users on different browsers. It’ll mostly be throwaway code if I’m leveraging local storage or this api, but I could run local storage entirely in the browser without messing with another thing I need to make sure is running.
So, if I need a multi user site and I want put together a hack to show some possibility, then sure. I think in that case I would probably just build some cheap nodejs apis into whatever dev server I’m using. The code would be less throwaway at that point.
Either way, good on you for building this out. It’s a cool concept and even if it’s a niche situation, maybe it’ll make someone’s life a little nicer. If you had pitched this use case, then it would have been fine and maybe informative. (And I would have never complained)
For all that you said, you need to do work to achieve it, that’s what injee cuts out and gives you in an instant.
Using browser local storage is actually less work in my opinion. For the other options, it’s a bit more work but not that much and the end result would be a lot more usable. (Especially with all the QuickStart options now)
My main problem is that business logic Id want to code into the backend would now be coded in the front end. Unless I’m going to throwaway all of this code, that’s going to be significantly more work to unwind. If I’m throwing it away, don’t care about security, and need to support multiple computers connecting then this is a good niche product for me.
There’s nothing wrong with it being designed for this niche. Also, I’m just giving you feedback because you asked for it