Really nice deep dive! I only wish there would be an official and polished language server from the lit team for code editors and IDE´s, because what we currently have makes it awful to work with lit for some parts. Otherwise than that Lit is awesome!
Agreed. I asked the Lit team and they said "We're starting to maintain the lit-analyzer and vs code plugin. Publishing a standalone language server probably makes sense" so it seems like this might be happening soon 🤞
Most of the heavy lifting is done by the browser already. Web components arose from the Extensible Web Manifesto (github.com/extensibleweb/manifesto) way of thinking: that browsers should expose standardized low-level APIs that allow library developers to build the kind of high-level APIs they think are appropriate. If the browser provided a standard templating API, it might be good for most use cases, but if you wanted to do something differently, it would be difficult to customize without going into user-land JS solutions.
@@vaadinofficial Correct but I'm taking about all of the things you've talked about regarding updating only what's necessary with all of the regexs etc.
@@vaadinofficial One video could show the changes introduced from 14 to 23. For the developers who didn't upgrade on each release but stayed on the LTS.
![[DevFest Nantes 2019] Building a Complex Application with Web Components and LitElement](/img/1.gif)
Really nice deep dive! I only wish there would be an official and polished language server from the lit team for code editors and IDE´s, because what we currently have makes it awful to work with lit for some parts. Otherwise than that Lit is awesome!
Agreed. I asked the Lit team and they said "We're starting to maintain the lit-analyzer and vs code plugin. Publishing a standalone language server probably makes sense" so it seems like this might be happening soon 🤞
Sounds to me like some of those optimization should take place on the browser itself
Most of the heavy lifting is done by the browser already. Web components arose from the Extensible Web Manifesto (github.com/extensibleweb/manifesto) way of thinking: that browsers should expose standardized low-level APIs that allow library developers to build the kind of high-level APIs they think are appropriate. If the browser provided a standard templating API, it might be good for most use cases, but if you wanted to do something differently, it would be difficult to customize without going into user-land JS solutions.
@@vaadinofficial Correct but I'm taking about all of the things you've talked about regarding updating only what's necessary with all of the regexs etc.
Imagine using Lit with Vite. Yeah, I'm talking about them rhyming.
I don't need to imagine, I do it all the time. It's excellent.
Vaadin 23 videos coming?
Definitely. Do you have any specific videos you’d like to see?
@@vaadinofficial One video could show the changes introduced from 14 to 23. For the developers who didn't upgrade on each release but stayed on the LTS.
Bro, you are a good professional, but a very weak speakesman. Sorry.
and your very bad at giving feedback :)