core VS material-web

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

For example, all the following design systems can be used without tooling (some of them provide ready-to-use bundles, others can be used through import maps): Google's Material Web, Microsoft's Fluent UI, IBM's Carbon, Adobe's Spectrum, Nordhealth's Nord, Shoelace, etc.

Guess there was a 1.0 3 weeks ago: https://github.com/material-components/material-web/discussi...

There is a new “official” one in the works here [1] that uses lots of the “latest and greatest stuff” and should be very fast when it’s finished (later this year). As far as I know it’s set to become the new default company wide implementation of Material on web.

[1] https://github.com/material-components/material-web

I'm using material-web web components inside a form with felte.dev

If you're going for full SSR and don't want to have to worry about JavaScript, I'd just grab the MDC web components library from Google. That's going to be the easiest time you'll have without implementing a front end framework.

Ultimately, I'd like to be able to write reasonably complex client/server web apps in Rust, so the next medium term thing on my list is web components (as a consumer). That'll allow a lot of existing Javascript components to be reused. For example: Microsoft Fast, Material Web Components and UI5.

Material Design (Google)