The author experimented with coding solely on AR glasses and a Linux environment running on their Android phone for two weeks. They used Nreal Air glasses for display, a Bluetooth keyboard and mouse, and Termux to access a Debian Linux environment on their phone. While acknowledging the setup's limitations like narrow field of view, software quirks, and occasional performance issues, they found the experience surprisingly usable for tasks like web development and sysadmin work. The portability and always-available nature of this mobile coding setup proved appealing, offering a glimpse into a potential future of computing. Despite the current drawbacks, the author believes this kind of mobile, glasses-based setup holds promise for becoming a genuinely productive work environment.
In a detailed blog post titled "Coding without a laptop: Two weeks with AR glasses and Linux on Android," the author recounts their two-week experiment of replacing their traditional laptop workflow with a combination of augmented reality (AR) glasses and a Linux environment running on their Android smartphone. The central motivation behind this endeavor was to explore the viability of a more mobile and potentially less cumbersome coding setup. The author meticulously documents their process, starting with the selection of hardware and software. They chose the Nreal Air AR glasses, highlighting their lightweight nature and relatively affordable price compared to other AR options on the market. For the software component, they opted for UserLAnd, an application that facilitates running a full Linux distribution on Android without requiring root access. Specifically, they installed an Arch Linux distribution within UserLAnd.
The setup process involved configuring the connection between the AR glasses and the phone, which involved enabling developer mode on the phone. The author then installed and configured a VNC server within their Arch Linux environment, enabling them to remotely access the Linux desktop from their phone's screen, mirrored within the AR glasses. This provided them with a virtual, large-screen experience within their field of vision.
The blog post then delves into the author's practical experiences using this setup for their daily coding tasks. They describe utilizing a Bluetooth keyboard and mouse for input, elaborating on the advantages and disadvantages of this input method in the context of their AR-based workspace. They discuss specific software they used within the Linux environment, including the Neovim text editor and the tmux terminal multiplexer, outlining how these tools contributed to their workflow.
The author further analyzes the performance of the setup, detailing both the positive aspects and the limitations they encountered. They commend the overall responsiveness of the system for tasks like web browsing, coding, and running command-line tools. However, they also acknowledge limitations, particularly with respect to more resource-intensive tasks, such as compiling larger projects. Battery life is also identified as a significant constraint, as the combination of the AR glasses, active phone screen, and running Linux distribution noticeably drained the phone's battery.
Finally, the author provides concluding reflections on their two-week experiment. They express optimism about the future potential of AR-based coding environments, particularly as hardware and software continue to evolve. While acknowledging that the current state of this technology isn't a perfect replacement for a traditional laptop for everyone, they suggest that it presents a compelling glimpse into the possibilities of more mobile and flexible coding workflows in the future. They also indicate potential areas for improvement, including better integration between AR devices and mobile operating systems, and further optimization of software for resource-constrained environments.
Summary of Comments ( 199 )
https://news.ycombinator.com/item?id=43985513
Hacker News commenters generally expressed skepticism about the practicality of the setup described in the article. Several pointed out the limitations of current AR glasses, including battery life, field of view, and input methods. Some questioned the real-world benefits over existing solutions like a lightweight laptop or tablet, particularly given the added complexity. Others highlighted the potential for distraction and social awkwardness. A few commenters expressed interest in the concept but acknowledged the technology isn't quite ready for prime time. Some discussed alternative approaches like using VNC or a lightweight desktop environment. The lack of details about the author's actual workflow and the types of tasks performed also drew criticism.
The Hacker News post "Coding without a laptop: Two weeks with AR glasses and Linux on Android" generated a moderate number of comments, discussing the practicality, potential, and limitations of the setup described in the linked blog post.
Several commenters expressed skepticism about the real-world usability of coding with AR glasses in their current state. One commenter pointed out the lack of comfortable input methods, highlighting the absence of a good keyboard and mouse replacement. They questioned the ergonomics of using a virtual keyboard or hand tracking for extended coding sessions. Another user echoed this sentiment, emphasizing the importance of tactile feedback for efficient typing and the strain that a purely visual interface could impose. The lack of peripheral vision when using current AR glasses was also mentioned as a significant drawback for coding, which often requires referencing multiple resources simultaneously.
However, some commenters recognized the potential future of such a setup. One acknowledged the current limitations but expressed excitement about the possibilities of AR for coding once the hardware and software mature. They envisioned a future where AR could overlay code onto the real world, enabling developers to interact with their projects in a more immersive and intuitive way. Another user suggested potential use cases like quick edits and debugging in situ, rather than full-fledged development. They also mentioned the possibility of using AR glasses for pair programming or remote collaboration.
The discussion also touched upon specific technical aspects. One commenter questioned the performance of running a full Linux distribution on Android, especially for resource-intensive tasks like compiling code. Another inquired about the specific hardware and software used in the blog post setup, highlighting the need for more details to replicate the experiment. Someone else mentioned the potential security implications of running Linux on Android, especially if used for sensitive projects.
Finally, a few comments focused on alternative approaches to mobile coding. One commenter suggested using an iPad with a keyboard as a more practical solution for coding on the go, while another mentioned the benefits of cloud-based development environments. These alternatives were presented as more mature and readily available solutions compared to the experimental AR glasses setup.