Andrey (azangru) wrote,
Andrey
azangru

Google has finally become ready to promote its Lit ecosystem properly. I thought they were going to make their announcements at the coming Google IO; but, to my surprise, they preempted that by holding a virtual event today where they announced the release of the new major version of the library, with the updates that address most of the concerns that I had when I tried to use LitElement in anger for the first time.

- There is a way to separate component's state from component's properties. Apparently it existed even before this update; but the docs weren't very clear on that. The docs were rather niggardly in the information they supplied, I must say.
- There is a proposal for a browser api to encapsulate the declarations of custom elements within their hosts. Which is clumsier than what we get with frameworks, but at least makes web components more suitable for large codebases.
- There is a convenient way to share common functionality between components.
- There is support of server-side rendering.

All in all, pretty uplifting stuff. But of course I am now entrenched in React at work.

Subscribe

  • (no subject)

    Wow, I never knew about this cultural reference in the Matrix (near the beginning, when Neo wakes up). A hat tip to postmodernism: (learned…

  • (no subject)

    Yesterday I learned... ...that if you press Ctrl-C in vim in the normal mode, it will actually show you a hint for how to quit vim. All those jokes…

  • (no subject)

    As I've said repeatedly here, Ben is great. He is a smart developer, an engaging conference speaker, and an entertaining conversationalist on…

  • Post a new comment

    Error

    default userpic
    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.
  • 0 comments