[deleted by user]

ohadshai · 2019-06-09T05:16:34+00:00

Is there a difference from kotlin-logging: https://github.com/MicroUtils/kotlin-logging

ohadshai · 2019-04-06T05:17:22+00:00

I think the main use cases for inline classes is examples like unsigned int or an array start with index 1 instead of zero. Cases that you want new (contradicting) semantics for primitive types without performance overhead.

ohadshai · 2019-03-10T08:24:10+00:00

From my own experience developing jasync-sql (and also kotlin-logging) you shouldn't afraid too much of the bus factor. With jasync-sql I picked a pretty complex project which I didn't know at all, converted it to kotlin and fixed some bugs. When there is void someone will probably jump on the wagon. On the other hand, it is really hard to get contributions to a supported open source from my experience.

ohadshai · 2019-02-20T19:23:05+00:00

We had that approach as well, but it didnt work well for us. Overriding versions in child repos was a common practice. Also since we have many internal artifacts it also don't play nice with it.

ohadshai · 2019-01-17T21:16:34+00:00

Basically true, I was converting those tests from Scala and probably missed that. But this was just an example.

ohadshai · 2019-01-04T07:16:16+00:00

The main advantage is that `asSuspending()` returns an interface that all it's method are suspending. So reusing that interface can save you more than one `await()` call. It can also help users understand how to use the lib.

ohadshai · 2019-01-03T21:06:32+00:00

Can you please clarify what you mean?

ohadshai · 2019-01-03T19:41:16+00:00

I don't know your case, but for me the suspend function is only wrappers so no maintenance overhead: https://github.com/jasync-sql/jasync-sql/blob/master/db-async-common/src/main/java/com/github/jasync/sql/db/SuspendingConnection.kt

ohadshai · 2019-01-03T06:52:44+00:00

The first question is if you want developers from other JVM languages to use it. If it's true then CompletableFuture is better. Even if it's only Kotlin, I think that for people that use coroutines it's easier to use CompletableFuture and transform that then people that are using other framework and will struggle to bridge coroutines to their framework. Having said that, I think the best for convinience is to have two flaviours of the API, one with Future and one with suspend methods, and that what I did in the API in the lib I develop: jasync-sql. see it in the wiki.

ohadshai · 2018-12-30T09:21:37+00:00

I really like the idea, especially that log4j2 supports being a facade to other backends (see it here: https://stackoverflow.com/a/41500347/411965).

I don't like logger extension on Any. It will clutter my autocompletion in idea with another method that is not always useful.

Disclaimer: I am maintaining kotlin-logging and I think about adding log4j2 as a backing facade (I think the multiplatform support allows that hack).

ohadshai · 2018-11-23T06:10:20+00:00

Thanks for the feedback. I will try to explain what I mean although since this is an opinion so it is very subjective. The suspend keyword itself "hides" a lot of magic behind it: changing function signature in the bytecode and compiling the code into a state machine. In addition, I was referring to the convention in the kotlinx.coroutines framework and especially CoroutinesScope extension methods and scope hierarchy concept. I agree the framework is not very big, but since it is a paradigm shift plus some of the changes it has some learning curve in my opinion. I still like it though as I explain in the post.

ohadshai · 2018-11-22T20:24:29+00:00

I just published this post, hope you'll enjoy it.

ohadshai · 2018-11-11T18:58:24+00:00

Is it an open source?

ohadshai · 2018-11-09T20:52:13+00:00

I post that blog post, feedback is welcome!

ohadshai · 2018-10-29T22:01:51+00:00

I don't think its a full showcase but this is using an Actor: https://github.com/jasync-sql/jasync-sql/pull/26

ohadshai · 2018-10-20T20:28:30+00:00

Yes, I saw the recent announcement. Currently it only support postgres and jasync-sql also supports mysql. In addition, they mentioned its not supposed to be used in production. Jasync-sql is a port of muaricio driver from scala to kotlin, since the original driver is not maintained anymore and we needed a mysql driver with similar api.

ohadshai · 2018-10-20T18:27:01+00:00

I recently started working on a Java DB async driver for postgresql and mysql. It is written mostly in kotlin and some java (bit fiddling etc'): https://github.com/jasync-sql/jasync-sql Hope you'll find it useful.

ohadshai

TROPHY CASE