The long story is that we want to keep iterating the Hilla development experience until we realize the full potential that we see in it. This means that we choose to focus on a single tech stack to avoid slowing down the iteration. Either Lit or React would be appropriate rendering solutions in that tech stack and we have chosen to focus on React since that’s what’s used by most of the potential users that we talk with.
We hope to eventually extend our reach to other technologies once we are really happy with how things work for the single stack that we are now focusing on. This applies both to frontend rendering solutions such as Lit, Vue or Angular as well as backend technologies such as Quarkus or Kotlin.
We remain committed to using Lit as our technology of choice for building reusable UI components for the web. We also keep the existing Lit support in Hilla working at the same level that it is on today. Some of the new features that we build are independent from the rendering library and will thus also be useful for those who use Hilla with Lit. Other things that we build are fundamentally based on React APIs and will thus only be useful for React users.