The discussion revolves around the practicality and necessity of HTTP/2, particularly its performance perks in relation to load balancing and the inherent challenges faced by developers. Key points include: - HTTP/2 offers features like duplex streams that provides benefits similar to WebSockets, but many browsers don’t support the necessary JavaScript API for these features. - Issues with load balancer support and security concerns, such as request smuggling, hinder wider adoption. - There's skepticism regarding the real-world benefits of HTTP/2 versus the complexity it introduces, especially with regards to connections and performance during high-demand scenarios. - The necessity for HTTPS with HTTP/2 may add latency, and many CDN providers have yet to implement HTTP/2 back to origins, limiting its use case further. Overall, while HTTP/2 introduces some advancements, its implementation challenges and a lack of strong support from browsers and infrastructure are significant obstacles to its widespread adoption. Developers feel an imbalance between the theoretical advantages versus practical deployment complexities; thus, there’s a call for clearer insights into when and how to effectively utilize HTTP/2 in modern web applications.