Hey! Just curious, what is the reason for having k...
# kilua
n
Hey! Just curious, what is the reason for having kilua-rpc instead of using [kotlinx-rpc](https://github.com/Kotlin/kotlinx-rpc). So far, I setup kotlinx and it works quite well.
r
Hi! Kilua RPC was created before kotlinx-rpc was announced. Also Kilua RPC was ported from KVision RPC interfaces, which has even longer history.
kilua-rpc supports many different servers, while kotlinx-rpc only Ktor at the moment.
I haven't used kotlinx-rpc, but looking at the docs I think kilua-rpc is still easier to use.
Still, if it works for you, there is no problem in using kotlinx-rpc. But there are some features you may miss - e.g. fullstack components.
n
Totally makes sense. Thanks! From all the things, I guess I will miss the tabulator support
p
Do I understand correctly that kilua-rpc client can be only web frontend in kotlin JS? This is an advantage of kotlin-rpc, that it can be used also from a desktop app (or another server or whatever). That is why would be cool if it would be also supported
r
Yes, kilua-rpc is only for JS and WasmJS clients.
I don't think there is anything that can be done to somehow "support" kotlinx-rpc, because it can be used. It just doesn't have some features, you already have in kilua-rpc.
n
In my small pet project, I have a couple of flows that are working. So I can confirm that nothing special is needed.
One small problem bothers me: I cannot upgrade to Kotlin 2.2 yet, as kotlin-rpc has been lagging behind for a while. With kilua-rpc, I could already have kotlin 2.2