MoQ is a new live media protocol that has garnered attention but isn’t a necessity for everyone. The author, who quit their job to work on MoQ, emphasizes that while the protocol is backed by various companies, it's essential to evaluate whether it genuinely solves any specific problems before adopting it. The piece advocates for a problem-driven approach in development, suggesting that technology should address real issues rather than being used for the sake of being trendy. The author criticizes various tech fads, pointing out that many solutions, like certain JavaScript frameworks or the blockchain hype, often fail to address actual needs. The author draws a clear line between different protocols like TCP, QUIC, and MoQ. TCP remains the go-to for reliable internet delivery, while QUIC offers some latency advantages at the cost of reliability. For most high-quality content, sticking with HTTP or WebSockets is advisable. MoQ may have its place, particularly for specific use cases like Twitch, where real-time interaction is prioritized over video quality. However, the author stresses the importance of understanding specific user needs before deciding on a protocol. For various scenarios—like live sports, conferencing, or production studios—the author provides tailored recommendations, urging builders to select the protocol that best fits their needs instead of jumping on the latest trend. The tone is frank, and the takeaway is clear: focus on solving real problems with the right tools rather than getting swept up in the excitement of the newest technology.