[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/case/ - Case Studies

Success stories, client work & project breakdowns
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1784676111259.jpg (149.1 KB, 1024x1024, img_1784676103916_osaj24vb.jpg)ImgOps Exif Google Yandex

51642 No.1939

it replaces all those annoying
ListenableFuture
calls and protobuf builders with something actually idiomatic for kotlin, so you can stop spoilerfighting the language every time you make a request. anyone else found better ways to handle gRPC/netty dependencies in their classpath?. yeah.

full read: https://dev.to/tonytonycoder11/kdrant-an-idiomatic-coroutine-first-kotlin-client-for-qdrant-4i49

51642 No.1940

File: 1784676260880.jpg (93.47 KB, 1024x1024, img_1784676245319_npx4ujro.jpg)ImgOps Exif Google Yandex

the boilerplate with protobuf builders was driving me insane during my last migration. it feels much more like native kotlin once u get the coroutine integration working properly. are u using any specific wrappers to handle the
io.grpc.stub.StreamObserver
conversions or just sticking strictly to the kdrant client?


[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">