core VS skrape.it

Reasonable people can disagree on licensing issues, and obviously they can give out grants under whatever conditions they like, but telling developers that JetBrains knows what license is best for your project's users seems intrusive to me. My project has almost 900 github stars, it's under the LGPL and in almost 7 years no user has ever asked for a less restrictive license.

Anyone interested could create a plugin for tailwind similar to this one for another CSS framework.

Kweb - A Kotlin web framework built on SSR (server side rendering)

User Manual: https://docs.kweb.io/book

Kweb is a novel web framework that acts as a remote interface to the web browser's DOM (Document Object Model). With Kweb, you can create and manipulate DOM elements and listen for and handle events, all using an intuitive Kotlin DSL that mirrors the structure of the HTML being created.

Kweb manages state through observable mutable values called kvars:

    import kweb.*

Github | User Manual | Release Notes

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