hi guys! which one lib is more mature: `exposed` o...
# server
d
hi guys! which one lib is more mature:
exposed
or
squash
? it seems both serve for same purpose.
exposed
is being maintained extensively at first sight, has more stars on github and reasonable documentation. but
squash
is used in all recent JetBrains demo apps like
kotlinconf-app
or
kotlin-fullstack-sample
. what would you suggest for beginners?
d
i was asking the same question a week ago with no clear answer. i started using
squash
since as you mention it’s in the examples, but now moved over to
exposed
because it looks more actively maintained.
👍 1
so far it’s working quite nice but has some limitations (i’m using the DAOs) that i still have to figure out how to circumvent properly. and the documentation is not as complete as it looks on first sight, at least once you have more specific requirements.
d
still better then nothing 🙂
d
I think squash was supposed to be more light weight, at least that's what I understood when I had looked into it..
f
JDBI 3.0 works great with Kotlin also (automatic data class mapping, etc)