this post was submitted on 25 Jul 2024
-12 points (22.7% liked)
Frontend Web Development
296 readers
1 users here now
Community to discuss stuff all things related to frontend web development. (sharing resources, discussion etc.)
founded 3 years ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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