Varun K. created a sprawling, unconventional video wall using 35 old Chromebooks, controlled by a single Raspberry Pi. He leveraged the Chromebooks' existing screens and minimal onboard processing, creating a distributed system where the Pi sends individual frames to each Chromebook over Wi-Fi. While acknowledging performance limitations like noticeable latency and occasional frame drops, Varun highlights the project's simplicity and low cost, achieved by repurposing readily available hardware and open-source software. The result is a functional, albeit quirky, video wall capable of displaying images, videos, and even simple animations across its unconventional canvas.
This project is a web-based recreation of Tom Dowdy's "Kaos", a screensaver from 1991. It features the same swirling, colorful lines and pulsating geometric shapes that made the original popular. Built with JavaScript and rendered on a canvas element, this modern homage aims to preserve and share the mesmerizing visual experience of Kaos with a new generation while offering a glimpse back in time for those familiar with the original.
HN commenters largely expressed nostalgia for the original Kaos screensaver and praised the recreation's faithfulness to it. Some shared memories of using it in the 90s, while others discussed technical aspects like the original's algorithm and the challenges of recreating it using web technologies. A few pointed out minor differences between the homage and the original, like the color palette and the behavior of the "fly" element. Several commenters appreciated the simplicity and hypnotic nature of the screensaver, contrasting it with modern, more resource-intensive alternatives. There was also some discussion about the legal implications of recreating copyrighted software, and whether screen savers are still relevant today.
The blog post presents benchmark results comparing input latency between Wayland and X11 using a custom-built input latency measurement tool. It concludes that Wayland exhibits consistently lower input latency than X11 across various desktop environments and configurations, even when accounting for composition latency. The author attributes Wayland's superior performance to its simplified architecture, which bypasses X11's legacy layers and allows for more direct communication between applications and the display server, leading to reduced overhead and quicker processing of input events. While acknowledging potential confounding factors and the limitations of the testing methodology, the results strongly suggest that Wayland delivers a more responsive user experience due to its inherent design advantages in input handling.
Hacker News users discussed the methodology and conclusions of the linked article comparing Wayland and X11 input latency. Several commenters questioned the fairness of the comparison, pointing out potential confounding factors like different compositor implementations (Sway vs. GNOME) and varying hardware configurations. Some suggested the benchmark wasn't representative of real-world usage, focusing on synthetic tests rather than common desktop tasks. Others highlighted the difficulty of accurately measuring input latency and the potential for subtle system variations to skew results. A few commenters shared their personal experiences, with some reporting noticeable improvements in latency under Wayland while others experienced no discernible difference. Overall, there was skepticism about the article's definitive claim of Wayland's superiority, with many calling for more rigorous and comprehensive testing.
This blog post explores using NetBSD's native graphics capabilities without relying on the X Window System (X11). The author demonstrates direct framebuffer access using libraries like wscons and libcaca for simple graphics and text output, highlighting the performance benefits and reduced complexity compared to a full X11 setup. This approach is particularly advantageous for embedded or resource-constrained systems, or situations where a minimal graphical interface suffices. The post details setting up a NetBSD virtual machine, configuring wscons, and provides code examples using libcaca to draw shapes and text directly to the screen, showcasing the simplicity and directness of this method.
HN commenters largely praised the elegance and simplicity of NetBSD's native graphics stack, contrasting it favorably with the complexity of X11. Several pointed out the historical context, noting that this approach harkens back to simpler times and offers a refreshing alternative to the bloat of modern desktop environments. Some expressed interest in exploring NetBSD specifically because of this feature. A few commenters questioned the practicality for everyday use, citing the limited software ecosystem that supports it. Others discussed the performance implications, with some suggesting it could be faster than X11 in certain scenarios. There was also discussion of similar approaches in other operating systems, such as Framebuffer and Wayland.
Summary of Comments ( 9 )
https://news.ycombinator.com/item?id=43221697
HN commenters were impressed by the author's ingenuity and dedication to the project, with several praising the "janky" yet functional nature of the setup. Some questioned the practicality and cost-effectiveness compared to purpose-built video wall solutions, noting potential issues with synchronization and performance. Others discussed alternative approaches, including using Raspberry Pis or older hardware, and offered suggestions for improvements like utilizing a more robust synchronization mechanism or exploring different software solutions. A few users shared their own experiences with similar projects, highlighting the challenges and rewards of DIY video walls. There was also some lighthearted banter about the "unhinged" nature of the project, embracing the unconventional approach.
The Hacker News post discussing "The most unhinged video wall, made out of Chromebooks" generated a number of comments, mostly expressing fascination and amusement at the project.
Several commenters focused on the practicality and cost-effectiveness of the setup. Some questioned the choice of Chromebooks, suggesting that smaller, cheaper single-board computers like Raspberry Pis would be a more suitable and economical alternative. They pointed out the relatively high cost of Chromebooks compared to these alternatives, especially considering the limited processing power needed for simply displaying video tiles. Discussions around power consumption and heat dissipation also emerged, with users speculating about the overall efficiency of the system.
The unconventional and "unhinged" nature of the project was a recurring theme. Commenters appreciated the creator's ingenuity and willingness to experiment, using terms like "mad genius" and "glorious hack." The visual impact of the video wall, particularly its size and the synchronization of content across multiple screens, was also highlighted.
Some commenters delved into the technical aspects, discussing the software and hardware involved in synchronizing the Chromebooks and displaying video across them. They explored potential improvements and alternative approaches, including using specialized video wall controllers or distributed rendering techniques.
A few comments touched on the potential applications of such a setup, ranging from artistic installations and public displays to monitoring dashboards and gaming setups. However, the general consensus seemed to be that the project was more of a fun experiment than a practical solution for most use cases.
Finally, several commenters expressed interest in seeing more details about the project, including the specific hardware and software used, the configuration process, and the challenges encountered during the build. This curiosity reflects the overall positive reception of the project and the community's appreciation for creative and unconventional technical endeavors.