• 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