Activity?
Closed this issue · 3 comments
Is this still maintained? Can it be downloaded via sbt? Why do the APIs not use Futures?
@kuba-- is the one who deveopled the early version. It hasn't been updated in a while, we're happy to accept pull requests.
I didn't update this for a long time.
Why no Futures? It's simple.
If you really want futures just write val f = Future { /* your code */ }
But if library force you to use futures you cannot escape form that. You will have nested futures and then flatmap, etc. and it's not always good.
Having current approach, it's up to you - wanna use futures, just wrap it Future{}; it's not painful.
Having many nested futures is not always good approach and I'm guessing that your application is already working in async mode, so every action is a Future.
I wrote influxdb-scala because I wanted to have sth. in Scala. and most of my interaction with influxdb is like fire-and-forget.
And also my intension was to keep it extremely simple (because less is exponentially more :)).
That makes sense. Thanks for the design explanation!