lit-element VS Svelte

Using vanilla JS or TS or using web components and want to have a framework-independent way of doing things? You can stick to the GraphQL codegen itself since it takes care of almost everything underneath. Or if you want, you can also use Apollo Client’s vanilla version @apollo/client/core. Apollo Elements does come with support for a lot of webcomponent libraries like Lit, Fast and Gluon or even without any of it and hence is quite flexible.

The LitElement framework is easy to use as a base class to create lightweight and faster web components for working with any framework. LitElement is yet another one of the top web development frameworks among developers for using lit-html for rendering into shadow DOM. It also adds API for managing attributes and properties. Let’s find out whether the framework is good enough for your project.

When you're working with Web Components through LitElement, it's usual firing events for sending messages between them. You can use either Standard or Custom events.

🔸lit-element - a simple base class for creating fast, lightweight web components;

Isn't this just Polymer Lit Elements rebranded? https://github.com/Polymer/lit-element

Web components are a good start, but it is better to use LitElement to build them in that case, instead of using it directly.

Other frameworks which are using the same principle are [lit-element](https://github.com/Polymer/lit-element) and [heresy](https://github.com/WebReflection/heresy). there are surely more but these are ones i've found when looking for inspiration.

Using a lit-element component:

React has introduced measures like batching state updates, background concurrent rendering and memoization to tackle this. My opinion is that the best way to solve the problem is by improving their reactivity model. The app needs to be able to track the code that should be re-run on updating a given state variable and specifically update the UI corresponding to this update. Tools like solid.js and svelte work in this manner. It also eliminates the need for a virtual DOM and diffing.

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

Svelte is a powerful web framework that offers a fresh approach to building web applications. Its simplicity, reactivity model, and built-in features make it an excellent choice for developers looking to create efficient and maintainable applications. By following this guide, you should now have a good understanding of how to get started with Svelte and build your first components, routes, and transitions. You can read more about svelte on the official Svelte website.

Use .NET features (especially dotnet watch) as a setup for a client-side Svelte application, starting from a simple C# console app.

Volar originally was Vue3's language support tool for VScode (I don't know about other editors). By today, volar has become a language indipendent framework to create language tools. It might still be a bit early for the dev with skill issues like me to use it and build some tools, but astro and svelte already use Volar to create their language tools.