skrape.it VS hexagon

What is wrong with skrape.it?

This includes many things that Kotlin makes use of, like String.invoke(block: () -> Unit) which is both an extension on String instances and makes uses of Kotlin's "ability" to move lambdas out of parentheses if they are the last argument (so something like log(lazyString: () -> String), can be used as log({ "message" }), or log { "message" }, @DslMarker (to allow a String.invoke(() -> Unit) block in the form of "it should behave well", only inside the context of a StringSpec.), infix funs (+ is infix operator fun plus(), with some slightly specific language handling because it's extremely common, infix fun shouldBe). This is using Kotest (https://kotest.io/docs/framework/writing-tests.html), but other tools like Ktor, Skrape.it (https://github.com/skrapeit/skrape.it), and more: https://kotlinlang.org/docs/type-safe-builders.html

I use skrape{it} (https://github.com/skrapeit/skrape.it) in my projects for 5 months now. Pretty good library IMO.Q

Hexagon is a Microservices Toolkit that aims to provide all you need to develop applications that run on Cloud environments.

Ktor is a project that's not primarily focused on application performance but developer performance. It seems to be sth different than what you want to achieve. I don't think a lot frameworks... or any other framework writes its own low level io stuff from scratch, they mostly use https://netty.io/ because there's not too much room for improvement and it's complete, battle tested and so on. I lately came across https://github.com/hexagonkt/hexagon which seems to have a very solid code base based on modules modules modules, is kotlin first and they have an adapter for netty. The usage of the naked http server seems to be as easy as it can be https://hexagonkt.com/port_http_server/port_http_server/ and they are even listed on techempower benchmarks https://github.com/hexagonkt/hexagon/ .

https://github.com/hexagonkt/hexagon A microservices toolkit written in Kotlin.