Rethinking the Local Network for Wireless Monitors: What Went Wrong and What Could Have Been
As technology rapidly evolves, one thing has become clear: despite the incredible advancements in wireless networking, the dream of truly wireless monitors that are seamlessly integrated into our local networks has largely remained unfulfilled. While we have technologies like Miracast and AirPlay, which allow for some level of wireless display functionality, they fall short when it comes to reliably handling modern tasks like office work, gaming, and multimedia streaming.
In this piece, I’ll explore why wireless monitors aren’t a reality yet, how the browser and terminal paradigms shaped our current situation, and how the idea of only transmitting differences between frames (as opposed to constant, full-frame updates) could change the game for both networking and display technologies.
From Terminals to Browsers: The Missed Opportunity
It’s hard to talk about the internet without mentioning terminals. In the early days of computing, terminals served as simple input/output devices, where commands were sent to a server, and text outputs were displayed. As graphical interfaces became more prominent, the X Window System brought graphical capabilities to terminals, but it was still heavily dependent on continuous data exchange between the server and client.
Fast forward to the late 1990s and early 2000s, when the web browser became the de facto way to display rich content. Here, HTML, CSS, and JavaScript emerged as the key technologies that made browsers function. But the problem was, and still is, that browsers were built on the model of refreshing entire pages—not sending incremental updates, even when the changes on the screen were minor.
Imagine if browsers had evolved with the ability to transmit only the differences between page states, similar to how modern video codecs transmit only the changes between frames. This would have drastically reduced the amount of data sent over the network, allowing for smoother interactions and faster updates. Such a system could have been revolutionary, not just for browsers, but for wireless display technologies.
The Client-Server Dilemma: Why Aren’t User Devices Servers?
One of the most interesting facets of early computer networking was the debate around client-server architectures. In the terminal days, a user’s machine acted purely as a client, sending commands to a server for execution. Over time, the notion of client-server evolved, but a key decision was made that heavily influenced the future: user machines would not act as servers.
While this decision was driven by security concerns—opening user machines up as servers would increase the attack surface—it ultimately slowed the development of decentralized computing. Early protocols like Gopher, which offered server-like capabilities on user machines, were eventually abandoned in favor of centralized architectures like the World Wide Web.
But imagine if user machines had retained server-like capabilities in a more secure, controlled way. With modern encryption and sandboxing techniques, the theoretical risk could have been mitigated, allowing users to serve content as easily as they consume it. This could have paved the way for more peer-to-peer communication, and in turn, for a wireless monitor ecosystem where displays seamlessly interact with other devices over local networks.
Why Wi-Fi Monitors Haven’t Happened (Yet)
Given the advancements in Wi-Fi technology, one would expect that wirelessly streaming a monitor across a local network would be a no-brainer. But there are some fundamental challenges that have prevented this from becoming widespread:
High Bandwidth and Latency: Streaming a monitor, particularly at high resolutions (4K, 144Hz) requires a significant amount of bandwidth. Wi-Fi, while fast, often competes with other devices on the network, leading to latency and reduced quality. Even Wi-Fi 6 isn’t optimized for the type of low-latency, high-bandwidth streaming required for wireless displays.
Compression Trade-offs: Current solutions like Miracast use compression to reduce bandwidth requirements, but this often comes at the cost of image quality and introduces latency. Without efficient real-time encoding and decoding, the experience of using a wireless display isn’t comparable to a wired one.
Event-Driven Rendering: Instead of continuously transmitting full-frame data, the solution could lie in transmitting state differences. In most office applications, such as typing in a word processor or browsing the web, the majority of the screen remains unchanged. By only sending the changes (deltas), the bandwidth could be drastically reduced. Even better, scrolling events could be detected at the OS level, ensuring only the necessary data is transmitted, rather than refreshing the entire screen during a scroll.
The Future of Wireless Monitors: Peer-to-Peer Rendering?
One promising direction for the future of wireless monitors lies in the concept of peer-to-peer rendering. Imagine a scenario where the operating system could detect when specific areas of the screen change, and only transmit those differences across the network. This could be applied to both wireless displays and remote work setups, where lightweight data transmission would enable fast, responsive interactions across devices.
The technical capability for this already exists in some forms—video codecs, remote desktop protocols, and web frameworks all leverage differential updates. If combined with modern Wi-Fi and OS-level hooks, the dream of a wireless monitor that can perform as well as a wired one may not be far off.
Conclusion: Revisiting the Old to Rethink the New
It’s fascinating to look back at the evolution of terminals, browsers, and client-server architectures and see where opportunities were missed. The decision to separate client from server on user devices, though well-intentioned, may have slowed innovation in areas like wireless display technologies. However, the ideas of transmitting deltas, leveraging event-driven rendering, and embracing peer-to-peer communication offer a potential roadmap for the future.
The reality is that we don’t need to reinvent the wheel—many of the concepts that could enable wireless monitors already exist. It’s just a matter of applying them in smarter, more optimized ways. As networking technologies like Wi-Fi 6E and Wi-Fi 7 mature, perhaps it’s time to revisit these old ideas with fresh eyes.
Let me know what you think! Would love to hear your thoughts on whether this model could finally bring wireless displays into mainstream office setups.
Follow this publication for more insights on the future of computing, networking, and how past ideas could shape tomorrow’s technology.