Simplicity. Adding layers to the stack can add serious complications to projects that sometimes just don't need it. Knex looks pretty cool and we'd love for the community to integrate HarperDB into this and other solutions like it. That said, ORMs lock developers into strict structures that limit what the application can do to what the ORM can do, rather than the underlying database. Personally, I believe that abstraction adds more complication than it's worth. That said, there are tools that aid in development with HarperDB that Margo mentioned in the article like the Node.js client and the React hook.
I like node API based stuff but I can tell you for sure Harper will never blow up if you guys don't open source it. I mean what can be so special and secrete about this system it is a node api and I don't know maybe the servers are kept in sync via graphql subscriptions I don't know but for sure it is not something that does not already exists. Also the Dashboard UI needs a Developer Asap. I recommend hiring an React dev and build a dashboard in React that looks like a modern one, the current dashboard I don't know what to say it looks Alpha. I hope you guys take this as feedback.
Thank you for the feedback, Ivan! The bundled dashboard UI included with HarperDB is deprecated. We have shifted our focus to the hosted HarperDB Studio, but chose to include the existing UI in the event that users may still want to use it. Our long term roadmap includes a refresh of the bundled UI and/or a packaged downloadable application similar to the hosted Studio.
Some comments have been hidden by the post's author - find out more
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.
Simplicity. Adding layers to the stack can add serious complications to projects that sometimes just don't need it. Knex looks pretty cool and we'd love for the community to integrate HarperDB into this and other solutions like it. That said, ORMs lock developers into strict structures that limit what the application can do to what the ORM can do, rather than the underlying database. Personally, I believe that abstraction adds more complication than it's worth. That said, there are tools that aid in development with HarperDB that Margo mentioned in the article like the Node.js client and the React hook.
I like node API based stuff but I can tell you for sure Harper will never blow up if you guys don't open source it. I mean what can be so special and secrete about this system it is a node api and I don't know maybe the servers are kept in sync via graphql subscriptions I don't know but for sure it is not something that does not already exists. Also the Dashboard UI needs a Developer Asap. I recommend hiring an React dev and build a dashboard in React that looks like a modern one, the current dashboard I don't know what to say it looks Alpha. I hope you guys take this as feedback.
Thank you for the feedback, Ivan! The bundled dashboard UI included with HarperDB is deprecated. We have shifted our focus to the hosted HarperDB Studio, but chose to include the existing UI in the event that users may still want to use it. Our long term roadmap includes a refresh of the bundled UI and/or a packaged downloadable application similar to the hosted Studio.