Our current planning suggests that I'll be able to give this considerable attention later in the year, but of course that isn't the same thing as sustained maintenance.
With that said, I would strongly prefer not to add any features to gRPC-Kotlin that are absent in gRPC-Java, to prevent future incompatibilities if gRPC-Java adds the same features in a different, incompatible form. Most feature requests I have seen for gRPC-Kotlin fail that criterion. (I'm not certain if the specific example of global exception handling is supported by gRPC-Java?) On Friday, February 7, 2025 at 4:43:05 AM UTC-8 Ramiro Aparicio Gallardo wrote: > > Hi, thanks for taking a look, yeah, the main problem is that there is no > active support for it, and everything gets derived from it, no replies for > the tickets, and no new features added (there are like 3 different tickets > requesting some way to add a global exception handler), dependencies are > not up to date.... > I am not aware of anyone considering creating a fork, but there are at > least 4 competing alternatives for models Kotlin code generation and > supporting libs because the official protobuf Kotlin models are not really > stylistic or easy to use, I think one of them provides grpc support but it > will not be that strange that given the lack of support, someone else would > do it. We can try contacting them but I am unsure if they would be willing > to help maintain the "official" grpc-kotlin version. And as you said given > the silence that reigns in the project it is difficult to gather a > community that helps, if there was at least some maintenance maybe it would > be enough to get some PRs for adding new features or fixing bugs. > > On Monday, February 3, 2025 at 10:33:47 PM UTC+1 Eric Anderson wrote: > >> On Mon, Feb 3, 2025 at 12:52 PM 'Ramiro Aparicio Gallardo' via grpc.io < >> grp...@googlegroups.com> wrote: >> >>> The situation is worse now: >>> * grpc-kotlin does not work with latest grpc-java version >>> >> >> I'm assuming you're referencing >> https://github.com/grpc/grpc-kotlin/issues/633 . That actually looks >> normal and I don't think you're blocked by any actions from grpc-kotlin. >> Add a dependency on io.grpc:grpc-stub:1.70.0 and you should be fine. >> >> * There is no support for editions 2023 >>> >> >> I added a comment to https://github.com/grpc/grpc-kotlin/issues/625 to >> mention this is a problem for grpc-java as well. I'd hope it is as easy as >> setting a few fields that "edition 2023 is supported;" gRPC didn't really >> care about proto2 vs proto3. >> >> * the last release is still missing in maven.org even when it was >>> released almost 6 months ago. >>> >> >> I think that's https://github.com/grpc/grpc-kotlin/issues/620 >> >> Maybe Jetbrains can come and help with the support or open it to the >>> community but at the current state it is very likely that a fork will be >>> needed sooner than later if there is no reaction from the gRPC team. >>> >> >> The release is definitely a problem and is a bit specialized because of >> permissions. But other than the release, part of the problem is >> (apparently; I don't think I have any extra insider knowledge) the amount >> of time being spent on it. If there's interest in a fork that would imply >> someone would need to spend time on it. Are you aware of people that should >> be considered to become maintainers of (or simply help) grpc-kotlin. I >> recognize that no merged PRs doesn't nurture maintainers, so there probably >> isn't "an obvious set of existing contributors." >> > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/grpc-io/b7f35e9c-ee10-4185-938d-a19e3a476d8en%40googlegroups.com.
