text stringlengths 0 1.36k |
|---|
**Alex Sexton:** No, I said let's not get ahead of ourselves, but... Thanks for listening this week, this has been JS Party. |
• Web Components: standard web platform components for building custom UI elements |
• Custom Elements: creating own reusable UI components with their own APIs |
• Shadow DOM: a DOM that exists inside a component, not exposed to developers |
• Benefits of Web Components: |
• Cleaner rendering and scoping |
• Reduced collisions between CSS styles |
• Faster performance on slower browsers and connections |
• Relationship with React and Ember: can use these libraries to create Web Components |
• Confusion between Polymer and Web Components: Polymer is a library built on top of Web Components |
• Web Components allow for more efficient and faster development with a wider audience reach |
• They provide native functionality not available in other frameworks like React or Ember |
• Shadow DOM allows for element-scoped CSS and improved performance |
• Web Components have unique lifecycle events and template tag usage |
• Google was involved in the initial development of Web Components, but it's a W3C specification |
• Conflation with Polymer led to incorrect assumptions about its size and complexity |
• Web Components may change the way tools are built on top of them, rather than just adapting existing ones |
• They offer improved modularity, composability, and scoping for web applications |
• Server-side rendering with rehydration for improved speed and SEO |
• JSConf family of conferences and their code of conduct |
• Conferences in the JavaScript community, including JSConf, RobotsConf, JSUnconf, Cascadia, and Empire |
• Decline of general-purpose conferences and rise of specialized conferences (e.g. React Conf) |
• Importance of diversity sponsorship and inclusive environments in conferences |
• Conferences can be difficult to organize on a large scale. |
• Speaking at conferences is accessible to anyone who applies themselves and is passionate about their topic. |
• There are various ways to get involved in speaking at conferences, including submitting talks and open sections. |
• The game "speak/attend/stream" was discussed as a way to decide how to engage with conferences (speaking, attending, or streaming). |
• Non-JS conferences were mentioned, such as OSCON, RubyFringe, GopherCon, StrangeLoop, FullStackFest, and RevConf. |
• There are two types of conferences: community-organized events and large-scale events run by media companies or corporations. |
• The quality and purpose of content differ between these two types of conferences. |
• O'Reilly conferences have a reputation for low-quality talks and high costs |
• Smaller community conferences often provide more passionate and relevant talks due to attendee motivation |
• Food options at larger events can be poor quality and expensive |
• Tips for conference organizers include finding catering-capable food trucks and planning ahead for large crowds |
• Advice for speakers includes being passionate about the topic, telling a story, and inspiring attendees rather than simply teaching them |
• p5.js library overview |
• Processing vs Processing.js vs p5.js |
• p5.js features (Canvas-based, interactive graphics, video/audio/webcam input) |
• Plug-ins (p5.dom, p5.sound, p5.serial, etc.) |
• Accessibility of p5.js for beginners and non-JS devs |
• Resources (The Coding Train YouTube channel, Lauren McCarthy's work, ITP programs) |
• Discussion of the Web App Sec mailing lists |
• Recommendation of Sarah Drasner's book on SVG animations |
• Brief mention of DataSketches and its connection to SVG stuff |
• End-of-episode wrap-up and promotion of live shows and ratings on iTunes |
**Mikeal Rogers:** Hey, everybody! Welcome to JS Party, where it's a party every week with JavaScript. We're gonna talk a bit about Web Components conferences and processing today. Cool, fun stuff! |
**Rachel White:** Yaay! |
**Alex Sexton:** Did you say Web Components conferences, so conferences specifically for Web Components? |
**Mikeal Rogers:** Yes, that's the topic; those aren't two topics. |
**Rachel White:** I love the conferences about radio buttons. \[laughter\] |
**Mikeal Rogers:** Alright, so... Let's get into Web Components and custom elements, and things. |
**Rachel White:** Shouldn't we say who we are? |
**Mikeal Rogers:** Oh yeah, that's right, that's right... People don't know who we are. I'm Mikeal Rogers, we've also go Alex Sexton - say hello. |
**Alex Sexton:** Hello. |
**Mikeal Rogers:** \[laughs\] We've also got Rachel While, say hello... |
**Rachel White:** Hello! |
**Mikeal Rogers:** We just brought the pace way down. It's getting like smooth jazz pace now. |
**Alex Sexton:** I actually think, Mikeal, that your lag is high today. |
**Mikeal Rogers:** Oh really, is that what it is? |
**Alex Sexton:** Yeah. |
**Mikeal Rogers:** Okay. |
**Alex Sexton:** Everyone else seems to be normal, and whenever we talk to you, it takes you a long time to reply. |
**Mikeal Rogers:** I apologize. Alex, why don't you tell us what Web Components are, and what the whole deal is with custom elements, and what the hell is a Shadow DOM? |
**Alex Sexton:** Web Components are the Web standards version of kind of the popular component-driven model that people like to develop web applications in today. So the best way to think of Web Components, in my opinion, is to think about the current web platform, and think about how the things are implemented behind ... |
In the past, we've had a button element - or a radio button element, or a checkbox, or a select menu - and in the really early days this wasn't true, but for the last long time, if you were to go look at the browser implementation of a select box or an input element, it's just HTML, CSS and JavaScript behind the scenes... |
Web Components are so you can make your own button, that has not quite an opaque of an API, but you can make your own components that are standalone that you can pull into a page and use just as if you were using a button or a select... You could use the Alex button or the Mikeal button, or the Mikeal select, or the cl... |
\[03:56\] We can get into some of the technical implementation details of how this works, but I also think you might have mentioned the Shadow DOM already, and that's really just the DOM that exists inside of the component, rather than to the developer once they're using your components. So if you think about the old b... |
**Rachel White:** So is it just rendering these components in a cleaner way than having to append all of those other things that exist inside of the regular component? |
**Alex Sexton:** Well, everything still exists. You could take away the idea of Web Components and Shadow DOM, and it would just be a larger DOM with a lot more stuff in it, with a lot more CSS scoping, and there's a lot more chance for bleeding together of certain things... But yeah, there's nothing super special abou... |
Right now a lot of the React and Ember model relies on whole, massive libraries being able to run and execute prior to be able to see or use anything on the site, where these Web Components can. Since they utilize more of the web stack, the web stack can do a better job of rendering them instantly without as much work ... |
**Rachel White:** So I'm trying to read this as you go through, because I've honestly -- I hear the term Shadow DOM thrown around a lot, and... |
**Alex Sexton:** It's a very cool word! |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.