23 replies

1. Nathan Knowler 33 min later

   @zachleat How do you wrangle web components? Do I need a specific lasso for that?

   1. Zach Leatherman 1 hr later

      @knowler a Ted lasso I think

2. maxfenton 41 min later

   @zachleat I still don’t get what they *are* and a year from now I’ll regret not trying to learn sooner.

   1. Zach Leatherman 1 hr later

      @maxfenton you should catch this talk when it comes out!!

3. Avalynn Gunn 🇵🇸 58 min later

   @zachleat I want to see reactive properties. I've been thinking of trying this with proxies or preact signals.

   1. Zach Leatherman 1 hr later

      @clarkgunn yes!! 🏆

4. castastrophe 58 min later

   @zachleat

   - How can they be used to create a more accessible web?
   - What are the most common mistakes made when building web components?
   - What performance costs do they come with and how do you weigh those pros and cons?

   1. Zach Leatherman 1 hr later

      @castastrophe excellent, thank you!! 🙌🏻

      1. castastrophe 1 hr later

         @zachleat Do you know where you might be giving this presentation?

         1. Zach Leatherman 2 days later

            @castastrophe A few upcoming places! https://www.zachleat.com/web/speaking/

5. Thomas Broyer 1 hr later

   @zachleat Would you say WebC components *are* web components? How would you describe the relationship between WebC (and @enhance_dev) and web components?

   1. Zach Leatherman 2 days later

      @tbroyer @enhance_dev I don’t want to go too far into tooling around web components in this talk but it’s probably most accurate to say that WebC (and others!) use conventions for server side rendering set forth by web components standards. Some overlap with how I think of SCSS -> CSS

6. Jon 1 hr later

   @zachleat I'd like to understand more about a strategy for web components within a design system and how styles can be shared and also how to communicate between components effectively.

7. Mike Aparicio 1 hr later

   @zachleat why

8. Thomas Randolph 1 hr later

   @zachleat (I am a huge WC booster) I already have framework X. Why would I add WC to my stack when X also does that, and my design system is in X?

   1. Thomas Randolph 1 hr later

      @zachleat this is probably too broad of a question, granted. But "use the platform, first" tends to get zero traction. What are the compelling reasons for WC at large software orgs?

9. cthos 🐱 2 hr later

   @zachleat as a web component fanatic, no, but I sure as hell want to see this thematic talk.

10. Private reply 10 hr later
11. Šime Vidas 15 hr later

    @zachleat https://twitter.com/raymondcamden/status/1525534538738319360 @raymondcamden

12. The Spicy Web 18 hr later

    @zachleat what (if any) difference might there be between "leaf" components (UI atoms, etc.) and "branch" components (more app-specific stuff, layouts, etc.)?

    What are some ways we can think about and communicate the value of "split" components (aka templates live only in SSG/SSR world, then extra client-side behavior gets sprinkled on top)?

13. Elly Loel 1 day later

    @zachleat HTML imports please? 🥺
    Or like declarative shadow-dom without the shadow-dom? 🙃
    I just want web components without the need for JS.

    ... Maybe the real question to be asking is more plugins for tools to use WebC, alas I can't yet have the joy of working with eleventy on every project 🥲

14. Hasan Ali 1 day later

    @zachleat what is the abstraction that web components are trying to solve? Is it to organize markup, behavior and styles for developers? If so, what benefits does it offer over a UI framework like SolidJS? Lastly, what is its overhead and how does it scale compared to something like SolidJS?

15. Wubbels 3 days later

    @zachleat is there such a thing as too big to be a web component?