My first Web Component: audio_playlist.js

I've learned quite early on to avoid jumping on the hype train, but the lesson truly stuck when I started working in web development. I got burned a few times and quickly grew a healthy distrust for any fancy new name that would draw the attention of the tech news sites, especially when it had to do with frontend work.1 I vaguely remember dismissing Web Components as yet another trendy buzzword and lumping them with all the fancy revolutionary frameworks that seemed to be coming out every week. That's the trouble with thought reflexes: sometimes they make it harder to sort the wheat from the chaff. I'll blame the general obsession with shiny new crap instead of any lack of curiosity on my part.2 I finally got to read about them at some point and my skepticism dropped as soon as I learned that they were actually part of the standard W3C specification, which meant it wasn't tied to some library likely to become obsolete in a few months. Reading on, I felt the allure of reusability, and…