Thank you for the great work. I have a couple ques...

# kotlinx-rpc

[niqo01]

Thank you for the great work. I have a couple questions:
I believe Kotlin-rpc is in the "experimental" state as defined here is that correct? I did not see the current state in the Readme.
Also is @Alexander Sysoev the only committer for now? I am trying to assess how much JB is invested in this for the time being.

[darkmoon_uk]

I have the same question - I know JB are doing a lot with their resources, but for me kotlinx.rcp is hands-down the most exciting Kotlin Ecosystem library to come along in a while and deserves more attention - at least to get the project over its current 'road bump' of Kotlin 2.x compatibility (a little consultation/help from #C7L3JB43G team maybe?)

RPC takes away a lot of manual protocol wrangling. As an individual dev, it's the difference between some full-stack projects being with my reach or not. Ergonomic comms is more foundational to me than some other library initiatives that appear to have more Devs.

Kudos to @Alexander Sysoev for championing the idea and carrying it forward to this stage.

[Dirk]

The status is displayed with the badge at the beginning of the README -> It is experimental

[niqo01]

I missed the badge, thank you.

[rocketraman]

Absolutely. When using Kotlin on both the frontend and backend, its just so simple to send the same types across the wire without worrying about defining REST or GraphQL APIs, and doing all the associated plumbing and conversions. With kotlinx-rpc, the only time one needs to use REST or GraphQL is when one is exposing a public API. A huge number of use cases just don't need the lossy conversions and complexity those protocols bring.

[Alexander Sysoev]

Hey! Yeah, I'm basically the solo full-time dev, and my focus is this lib. That means that we are fully invested, but if I go on a trip or two (like I just did), the work stop for a while 😅

[darkmoon_uk]

Phew - glad to learn that's where you went @Alexander Sysoev 🌴 Welcome back 🙂