schizanon, 7 months ago (edited 7 months ago) to random

It's cool that #Lit is integrating with #Signals.

It feels like we've been circling around this design pattern for decades; they've been called Observables, Pub/Sub, State, Context, etc.

STOKED to hear that there's discussion around standardizing and adding Signals to the #webPlatform!

https://www.youtube.com/live/ri9FEl_hRTc?si=-oztbFGgLG0f9aXJ&t=1636

#webDev #lit #litHTML #litElement #buildWithLit #javaScript #web #react #preact #js #reactjs

schizanon, 7 months ago to javascript

It's super cool that #Lit is supporting standard #javaScript #decorators, but I'm still not going to use them!

Maybe one day when they don't need to be transpiled anymore.

#webDev #buildWithLit #litHTML #litElement #js

schizanon, 7 months ago (edited 7 months ago) to CSS

I think that #shadowDOM solves #css's problems and #lit is right to scope styles to the element.

#webDev #web #html #litElement #lithtml

schizanon, 7 months ago (edited 7 months ago) to react

#lit is getting a "context" api https://www.npmjs.com/package/@lit/context

It seems to work like #React #Context, but it's an open standard that other #webComponent frameworks can apparently implement.

#javaScript #js #webDev #web #lithtml #litelement #webComponents

fogoplayer, 10 months ago to random

One thing that gets me really excited about #webcomponents is the ability to change course.

I had a project written in #vanillajs , but that was a pain, so I started writing new code using #webcomponents . But that was still a pain, so I decided to write any new components using #litelement .

For my next project I’m thinking about using #hauntedjs and #ionicframework , but there’s peace of mind knowing that if I don’t like it I can go back to #litelement or #vanillajs .