<The Ktor Roadmap for 2024> As in 2023 and 2022, w...
# feed
r
The Ktor Roadmap for 2024 As in 2023 and 2022, we have been working on a roadmap for our development of Ktor for the year ahead. In the interests of transparency and accountability, we would like to share our plans with you here. Our ongoing plan Our ongoing plans and goals for Ktor remain consistent with previous years. We aim […]
slow parrot 11
🎉 6
🫤 2
a
Aren’t OpenTelemetry plugins actually out?
a
I was under the impression HTTP2 without TLS was also on the roadmap, but it’s not there :(
j
Whoa. Dependency injection and transactions! Are they trying to compete with spring? :)
d
🫤 DI? Meh... DI frameworks typically obfuscate how code is working: I continue to find them unnecessary with Kotlin and it's disappointing that Ktor appears to be starting down a path of making DI framework usage a 'recommended practice'. Should have stayed agnostic.
@Arjan van Wieringen Don't give up hope - it could be that HTTP2 w/o TLS is still in the running but isn't considered a 'headline feature' enough to appear in the Roadmap. I am also looking forward to WebSockets support for WASM and it was suggested to me by a JB Dev that this is still set to appear in the full 3.0.0 release even though it's not on the 2024 roadmap.
a
@darkmoon_uk I am thrilled about DI. But I agree with your sentiment. It is an abstraction that should only be needed in some cases. In Compose I must say I use it all the time.
s
@Antonio Acuña Prieto yeah i think with java agent instrumentation and for netty (https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/ktor/ktor-2.0/library) . Better to have official support as everybody is moving to OTEL for trace, metrics & logging.
a
@suresh yeah I noticed that later! Btw, that library doesn’t work with Ktor 3… Do we know when will the official instrumentation library out? If not I can adapt the Ktor 2 library to work with Ktor 3, actually is just a line 🤣