Post

Duffeh
@duffeh.bsky.social

I feel like Ai usage will cause more to use it as well, just based on the information it has. Yet I constantly have it try to gaslight me.

Aboogail Screamini
@abbeyperini.dev

Oh, I didn't realize unsupported, grandiose statements were trying to start a conversation. Does it have the best ecosystem or is it just the most popular with the most options? Why do you believe maintaining 2 virtual DOMs as a reactivity system is the best architectural decision over Proxies?

Charles Villard
@charlesvillard.co

As someone actively using React, this is the most lukewarm, unproductive take. The ecosystem has lots of libraries, 90% of which have no adoption. Architecturally, it's stagnating. If companies like Okta, for example, can't be arsed to support major React frameworks, what's so great about it?

Ryan
@rschristian.dev

I don’t know if it’s fair to claim it’s stagnating, React has made a lot of changes over the last few years and created lots of opportunities for large architectural changes in apps IME, most of that hasn’t landed with the average user but it wasn’t for a lack of trying.

Charles Villard
@charlesvillard.co

I can concede a messaging problem about their changes, but I can't say the core team has done much outside of supporting RSCs which is what I think you're referring to. What have they done to address performance or bundle size of late? From what I can see, not a ton.

Matija Marohnić
@silvenon.com

I wanna try Astro + Solid soon, that would be my first time for both. Astro might be THE missing meta framework for many struggling apps who weren’t able to pull off single render, islands are exactly what I needed.

Aboogail Screamini
@abbeyperini.dev

This post brought to you by a blog comment saying Pinia and Valtio aren't "proper state management" but "Zustand, Jotai, or even just careful use of useContext" are proper. 👀

Joe Dakroub
@dakroub.co

Lit is a terrific framework. More people need to know about Custom Elements to really appreciate it. My favorite too.

Danny Engelman 🌷🏍️🛥️
@engelman.nl

Its not Lit that make Custom Elements terrific. native Custom Elements are terrific by themselves, Lit is just sugar that saves you work, like jQuery once was for front-end development. But I am biased, only done native Web Components for the past 10 years.

Joe Dakroub
@dakroub.co

With you there. I just really think Custom Elements have gotten buried for so many developers and really thought having a framework like Lit would put a big spotlight on just how cool CEs are. Most devs I know or work with, know little-to-nothing about them.

Duffeh
@duffeh.bsky.social

Does lit use shadow Dom, and is it easy to set the internals of elements like form submit buttons. Someone mentioned it to me the other week but not looked. I really like using Astro for initial html (could be any html), and using web components to add the interactivity parts at the moment.

Konnor Rogers
@konnorrogers.com

If you're looking for a reference, this is how we do it in Web Awesome to get *as close as possible* we copy all attributes, inject the button at the same level as the `<wa-button>` in the light dom, and then send a `.click()` to it. the only thing that will really mismatch is checking the tag.

Duffeh
@duffeh.bsky.social

I don't think it was a component that was a button, but hosted the button in shadow root, but didn't submit the light dom form outside of it. But that is really interesting.

Sam Rose
@samwho.dev

It uses shadow DOM by default, easy to opt out of if you want to. Unsure about your button question.