Hey everyone, We are announcing the future of our ...
# kodein
s
Hey everyone, We are announcing the future of our libraries, our focus, and our recent reflections. https://medium.com/kodein-koders/moving-forward-with-the-kodein-open-source-initiative-9fc4f6160c84
πŸ‘€ 5
πŸ’™ 3
πŸ‘ 4
m
Thanks for the openness and the awesome work
πŸ‘ 2
j
I did mention the Kotlin Dependency Injection Dependency Injection framework on some presentation a while ago πŸ˜„ glad to see it returned to its original name πŸ™‚ Btw if you specifically mention "we ask that you first try Kodein-DB in non-critical applications" people are more reluctant to use it πŸ˜„ perhaps change that, also perhaps change the fact that we should use it in server applications (or why wouldn't we? πŸ™‚ )
πŸ‘ 1
d
Hi @salomonbrys, do you intent to ship the new kodein-db with a synchronization feature? My use-case is using kodein-db on my client applications and have some kind of replication between those and some server repositories. Do you have examples of that already on the current kodein-db? Also, I've seen the issue https://github.com/Kodein-Framework/Kodein-DB/issues/15, how difficult would it be for me to hack kodein-db to have a level.js based LevelDB backend in my browser applications? Thanks for you help. PS: I might be interested in contributing to the new kodein-db.
s
Hi. Yeah, we intend to provide a sync feature, but not in the near future. JS would be quite complicated I think. I'd advise using Firebase at the moment.
r
MongoDB realm would be another option for sync that supports KMM (caveat: I've never used it, no endorsement is implied)