I'm not very familiar with loopback but I try to show up some key differences:
-Setup:
You need to setup and configure each loopback project yourself.
the kiss backend is usable out of the box (selfhosted or as a service)
-Realtime:
As far as I know loopback only does REST. In kissjs everything will be realtime.
-model definitions:
In Loopback you have to create endpoints for every entity you want to have crud methods for. eg. you want to save Todos and Bookmarks, then you have to setup your loopback instance to handle that. With kissjs you don't have to do that. you can easily access any kind of collection from the client and only define access control. The data layer is more comparable to firebase/firestore
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.
I'm not very familiar with loopback but I try to show up some key differences:
-Setup:
You need to setup and configure each loopback project yourself.
the kiss backend is usable out of the box (selfhosted or as a service)
-Realtime:
As far as I know loopback only does REST. In kissjs everything will be realtime.
-model definitions:
In Loopback you have to create endpoints for every entity you want to have crud methods for. eg. you want to save Todos and Bookmarks, then you have to setup your loopback instance to handle that. With kissjs you don't have to do that. you can easily access any kind of collection from the client and only define access control. The data layer is more comparable to firebase/firestore