The Evertop is a DIY open-source project aiming to create a modern, portable, and extremely low-power IBM XT compatible computer. It features a 4.2" e-ink display, mechanical keyboard, and boasts over 100 hours of battery life. Based on a Raspberry Pi Pico microcontroller emulating an NEC V20 processor, it can run original IBM XT software and DOS games. The project includes custom-designed PCBs and 3D-printed case files, making it reproducible for others. While still under development, the Evertop represents a unique blend of retro computing and modern hardware for a highly portable and energy-efficient experience.
This blog post details the creation of "Bayleaf," a custom-built, low-profile, wireless split keyboard. The author prioritized a slim design, opting for Choc low-profile switches and a custom PCB to minimize thickness. They used Kailh Choc Red switches and keycaps from MBK. The keyboard halves communicate wirelessly using the nice!nano microcontroller and connect to a computer via Bluetooth. The build process involved designing the PCB, 3D printing a case, and flashing the firmware. The result is a compact and portable split keyboard tailored to the author's preferences for ergonomics and aesthetics.
Hacker News users generally expressed interest in the Bayleaf keyboard, praising its low profile and split design. Several commenters compared it favorably to other low-profile keyboards like the Keychron K1 and K3, highlighting the Bayleaf's even thinner form factor. Some questioned the key travel and overall feel, expressing a desire for more details on those aspects. Others discussed the challenges of designing and manufacturing such a slim keyboard, particularly regarding keycap compatibility and battery life. A few users also showed interest in alternative layouts and the possibility of open-sourcing the design. Several comments focused on the keyboard's aesthetics, with some finding it appealing while others considered it too plain.
A hobbyist detailed the construction of a homemade polarimetric synthetic aperture radar (PolSAR) mounted on a drone. Using readily available components like a software-defined radio (SDR), GPS module, and custom-designed antennas, they built a system capable of capturing radar data and processing it into PolSAR imagery. The project demonstrates the increasing accessibility of complex radar technologies, highlighting the potential for low-cost environmental monitoring and other applications. The build involved significant challenges in antenna design, data synchronization, and motion compensation, which were addressed through iterative prototyping and custom software development. The resulting system provides a unique and affordable platform for experimenting with PolSAR technology.
Hacker News users generally expressed admiration for the project's complexity and the author's ingenuity in building a polarimetric synthetic aperture radar (PolSAR) system on a drone. Several commenters questioned the legality of operating such a system without proper licensing, particularly in the US. Some discussed the potential applications of the technology, including agriculture, archaeology, and disaster relief. There was also a technical discussion about the challenges of processing PolSAR data and the limitations of the system due to the drone's platform. A few commenters shared links to similar projects or resources related to SAR technology. One commenter, claiming experience in the field, emphasized the significant processing power required for true PolSAR imaging, suggesting the project may be closer to a basic SAR implementation.
The "R1 Computer Use" document outlines strict computer usage guidelines for a specific group (likely employees). It prohibits personal use, unauthorized software installation, and accessing inappropriate content. All computer activity is subject to monitoring and logging. Users are responsible for keeping their accounts secure and reporting any suspicious activity. The policy emphasizes the importance of respecting intellectual property and adhering to licensing agreements. Deviation from these rules may result in disciplinary action.
Hacker News commenters on the "R1 Computer Use" post largely focused on the impracticality of the system for modern usage. Several pointed out the extremely slow speed and limited storage, making it unsuitable for anything beyond very basic tasks. Some appreciated the historical context and the demonstration of early computing, while others questioned the value of emulating such a limited system. The discussion also touched upon the challenges of preserving old software and hardware, with commenters noting the difficulty in finding working components and the expertise required to maintain these systems. A few expressed interest in the educational aspects, suggesting its potential use for teaching about the history of computing or demonstrating fundamental computer concepts.
Eki Bright argues for building your own internet router using commodity hardware and open-source software like OpenWrt. He highlights the benefits of increased control over network configuration, enhanced privacy by avoiding data collection from commercial routers, potential cost savings over time, and the opportunity to learn valuable networking skills. While acknowledging the higher initial time investment and technical knowledge required compared to using a pre-built router, Bright emphasizes the flexibility and power DIY routing offers for tailoring your network to your specific needs, especially for advanced users or those with privacy concerns.
HN users generally praised the author's ingenuity and the project's potential. Some questioned the practicality and cost-effectiveness of DIY routing compared to readily available solutions like Starlink or existing cellular networks, especially given the complexity and ongoing maintenance required. A few commenters pointed out potential regulatory hurdles, particularly regarding spectrum usage. Others expressed interest in the mesh networking aspects and the possibility of community-owned and operated networks. The discussion also touched upon the limitations of existing rural internet options, fueling the interest in alternative approaches like the one presented. Several users shared their own experiences with similar projects and offered technical advice, suggesting improvements and alternative technologies.
Summary of Comments ( 166 )
https://news.ycombinator.com/item?id=43757037
Hacker News commenters generally expressed enthusiasm for the Evertop project, praising its unique combination of retro computing and modern e-ink technology. Several highlighted the impressive battery life and the appeal of a distraction-free writing device. Some questioned the practicality given the slow refresh rate of e-ink, particularly for gaming, while others suggested improvements like backlighting and a more ergonomic keyboard. A few commenters expressed interest in similar projects using different retro hardware, such as the Apple II or Commodore 64. There was also discussion about the challenges of sourcing parts and the potential market for such a niche device. Several users shared their personal experiences with similar e-ink projects and offered technical insights.
The Hacker News post about the Evertop, an e-ink IBM XT clone, generated a fair amount of discussion, with many commenters expressing enthusiasm for the project.
Several users focused on the impressive battery life. One commenter questioned how 100+ hours was achieved, prompting a reply explaining that the low-power nature of e-ink displays is the primary contributing factor. This led to further discussion about the power consumption of different components in the system and general power optimization strategies for low-power computing.
The choice of an XT clone as the basis for the project also sparked conversation. Some users reminisced about their experiences with XT machines, while others questioned the practicality of the platform in a modern context. One commenter suggested that a more modern, but still low-power, platform like a Raspberry Pi might be a better choice, offering more flexibility and software options. This prompted counter-arguments about the simplicity and robustness of the XT architecture, and its suitability for specific use cases where a full-fledged operating system isn't necessary.
The e-ink display itself was a major point of interest. Some commenters expressed concerns about the refresh rate and its limitations for certain applications, particularly those involving animation or video. Others highlighted the benefits of e-ink in terms of readability in sunlight and low power consumption, suggesting applications like e-readers or dedicated coding environments. The discussion also touched upon the different types of e-ink displays and their varying characteristics.
Several commenters expressed interest in purchasing an Evertop, inquiring about pricing and availability. There was also discussion around the potential for DIY builds, with some users sharing links to similar projects and resources.
Finally, the developer of the Evertop, Eric Jenott, participated in the thread, answering questions about the project's design choices, technical specifications, and future plans. This direct interaction with the creator added significant value to the discussion, providing insights not available elsewhere.