Yes, they are essentially identical, it's about giving a choice. Also, those libraries focus (mostly) on the front-end part. In Kretes, I'd like to provide tool

Yes, they are essentially identical, it's about giving a choice. Also, those libraries focus (mostly) on the front-end part. In Kretes, I'd like to provide tools/methods that cover the whole stack so to speak. This is especially visible for newcomers. A Vue.js tutorial may show you how to build the UI, but then you need to figure out how to bring in and persist the data, or how to connect to an API, etc. This isn't to say that such article should cover everything, but I have an impression that the industry requires or rather forces specialization too early, i.e. before people have a chance to understand the big picture. Kretes is about arranging different pieces together so that they are ready to use right away, even if you know how to configure them on your own, you don't need to and can focus on solving the actual business needs of your application. Disclaimer: As the project is in early alpha, this promise is not yet fully fulfilled. :)