The RISC OS GUI, developed by Acorn, prioritizes speed and efficiency through cooperative multitasking and a unique event handling model. Its distinctive drag-and-drop interface, involving iconic "icons" for applications, files, and even system settings, allows direct manipulation of objects and actions. Menus, invoked by clicking and holding on the desktop or objects, offer context-sensitive options, further streamlining interaction. While unconventional compared to prevalent windowing systems, RISC OS emphasizes minimal overhead and direct user control, leading to a responsive and arguably intuitive experience.
This website hosts a browser-based emulator of the Xerox NoteTaker, a portable Smalltalk-78 system developed in 1978. It represents a significant step in the evolution of personal computing, showcasing early concepts of overlapping windows, a bitmapped display, and a mouse-driven interface. The emulation, while not perfectly replicating the original hardware's performance, provides a functional recreation of the NoteTaker's software environment, allowing users to explore its unique Smalltalk implementation and experience a piece of computing history. This allows for experimentation with the system's class browser, text editor, and graphics capabilities, offering insight into the pioneering work done at Xerox PARC.
Hacker News users discuss the Smalltalk-78 emulator with a mix of nostalgia and technical curiosity. Several commenters reminisce about their experiences with early Smalltalk, highlighting its revolutionary impact on GUI development and object-oriented programming. Some express interest in the NoteTaker's unique features, like its pioneering use of a windowing system and a mouse. The practicality of NoteTaker's hardware limitations, particularly its limited memory, is also discussed. A few commenters delve into specific technical details, like the differences between Smalltalk-72, -76, and -78, and the challenges of emulating historic hardware. Others express appreciation for the preservation effort and the opportunity to experience a piece of computing history.
GTK developers are revitalizing their accessibility efforts. After a period of stagnation, they are focusing on modernizing the ATK implementation to better support assistive technologies. This involves adopting a more declarative approach, improving performance, and addressing long-standing bugs. They aim to create a robust and future-proof accessibility framework for GTK4 and beyond, ensuring applications built with GTK are usable by everyone. Key improvements include support for new accessibility interfaces, improved text attribute handling, and fixes for issues related to keyboard navigation and widget roles. This renewed commitment signifies a positive step towards making GTK applications more inclusive.
Hacker News users generally praised GTK's commitment to accessibility improvements. Several commenters with disabilities shared personal anecdotes highlighting the importance of such efforts, emphasizing how seemingly small changes can significantly impact their daily computer usage. Some expressed excitement for specific features like improved keyboard navigation and screen reader compatibility. A few users also offered constructive criticism, suggesting areas for further improvement, including better documentation and more consistent cross-platform support. One commenter questioned the efficacy of relying on Orca and AT-SPI, suggesting alternative approaches. Overall, the sentiment was positive, with users appreciating GTK's ongoing dedication to accessibility.
The blog post explores the recently released and surprisingly readable Macintosh QuickDraw and MacPaint 1.3 source code. The author dives into the inner workings of the software, highlighting the efficient use of assembly language and clever programming techniques employed to achieve impressive performance on limited hardware. Specific examples discussed include the rectangle drawing algorithm, region handling for complex shapes, and the "FatBits" zoomed editing mode, illustrating how these features were implemented with minimal resources. The post celebrates the code's clarity and elegance, demonstrating how the original Macintosh developers managed to create a powerful and user-friendly application within the constraints of early 1980s technology.
Hacker News commenters on the MacPaint source code release generally expressed fascination with the code's simplicity, small size, and cleverness, especially given the hardware limitations of the time. Several pointed out interesting details like the use of hand-unrolled loops for performance and the efficient drawing algorithms. Some discussed the historical context, marveling at Bill Atkinson's programming skill and the impact of MacPaint on the graphical user interface. A few users shared personal anecdotes about using early Macintosh computers and the excitement surrounding MacPaint's innovative features. There was also some discussion of the licensing and copyright status of the code, and how it compared to modern software development practices.
Blue95 is a passion project aiming to recreate the nostalgic experience of a late 90s/early 2000s home computer setup. It's a curated collection of period-accurate software, themes, and wallpapers, designed to evoke the look and feel of Windows 95/98, packaged as a bootable ISO for virtual machines or physical hardware. The project focuses on free and open-source software alternatives to commercial applications of the era, offering a curated selection of games, utilities, and creative tools, all wrapped in a familiar, retro aesthetic. The goal is to capture the essence of that era's computing experience – a blend of discovery, simplicity, and playful experimentation.
Hacker News users generally expressed nostalgia and appreciation for Blue95's aesthetic, recalling the era of Windows 95 and early internet experiences. Several commenters praised the attention to detail and accuracy in recreating the look and feel of the period. Some discussed the practical limitations of older hardware and software, while others reminisced about specific games and applications. A few users questioned the project's purpose beyond nostalgia, but overall the reception was positive, with many expressing interest in trying it out or contributing to its development. The discussion also touched on the broader trend of retro computing and the desire to revisit simpler technological times.
Adding a UI doesn't automatically simplify a complex system. While a UI might seem more approachable than an API or command line, it can obscure underlying complexity and create a false sense of ease. If the underlying system is convoluted, the UI will simply become a complicated layer on top of an already complicated system, potentially making it even harder to use effectively. True simplification comes from addressing the complexity within the system itself, not just providing a different way to access it. A well-designed UI for a simple system is powerful, but a UI for a complex system might just make it a prettier mess.
Hacker News users largely agreed with the article's premise that self-serve UIs aren't always the best solution. Several commenters shared anecdotes of complex UIs causing more problems than they solved, forcing users into tedious configurations or overwhelming them with options. Some suggested that good documentation and clear examples are often more effective than intricate interfaces. Others pointed out the importance of considering the user's technical skill and the specific task at hand when designing interfaces, arguing for simpler, more guided experiences for less technical users. A few commenters also discussed the trade-off between flexibility and ease of use, acknowledging that powerful UIs can be valuable for expert users while remaining accessible to beginners. The idea of "no-code" solutions was also debated, with some arguing they often introduce limitations and can be harder to debug than traditional coding approaches.
The PuTTY iconography uses a stylized computer terminal displaying a kawaii face, representing the software's friendly nature despite its powerful functionality. The different icons distinguish PuTTY's various tools through color and added imagery. For instance, PSCP (secure copy) features a document with a downward arrow, while PSFTP (secure file transfer protocol) shows a pair of opposing arrows, symbolizing bi-directional transfer. The colors roughly correspond to the traffic light system, with green for connection tools (PuTTY, Plink), amber for file transfer tools (PSCP, PSFTP), and red for key generation (PuTTYgen). The overall design prioritizes simplicity and memorability over strict adherence to real-world terminal appearances or symbolic representation.
Hacker News users discuss Simon Tatham's blog post explaining the iconography of PuTTY's various tools. Several commenters express appreciation for Tatham's clear and detailed explanations, finding the rationale behind the choices both interesting and amusing. Some discuss alternative iconography they've encountered or imagined, while others praise Tatham's software and development style more generally, citing his focus on simplicity and functionality. A few users share anecdotes of misinterpreting the icons in the past, highlighting the effectiveness of Tatham's explanations in clarifying their meaning. The overall sentiment reflects admiration for Tatham's meticulous approach to software design, even down to the smallest details like icon choices.
This 1989 Xerox PARC paper argues that Unix, despite its strengths, suffers from a fragmented environment hindering programmer productivity. It lacks a unifying framework integrating tools and information, forcing developers to grapple with disparate interfaces and manually manage dependencies. The paper proposes an integrated environment, similar to Smalltalk or Interlisp, built upon a shared repository and incorporating features like browsing, version control, configuration management, and debugging within a consistent user interface. This would streamline the software development process by automating tedious tasks, improving code reuse, and fostering better communication among developers. The authors advocate for moving beyond the Unix philosophy of small, independent tools towards a more cohesive and interactive system that supports the entire software lifecycle.
Hacker News users discussing the Xerox PARC paper lament the lack of a truly integrated computing environment, even decades later. Several commenters highlight the continued relevance of the paper's criticisms of Unix's fragmented toolset and the persistent challenges in achieving seamless interoperability. Some point to Smalltalk as an example of a more integrated system, while others mention Lisp Machines and Oberon. The discussion also touches upon the trade-offs between integration and modularity, with some arguing that Unix's modularity, while contributing to its fragmentation, is also a key strength. Others note the influence of the internet and the web, suggesting that these technologies shifted the focus away from tightly integrated desktop environments. There's a general sense of nostalgia for the vision presented in the paper and a recognition of the ongoing struggle to achieve a truly unified computing experience.
This video showcases a young, energetic Steve Ballmer enthusiastically pitching the then-new Microsoft Windows 1.0. He highlights key features like the graphical user interface, multitasking capabilities (running multiple programs simultaneously), and the use of a mouse for easier navigation, contrasting it with the command-line interface prevalent at the time. Ballmer emphasizes the user-friendliness and productivity gains of Windows, demonstrating basic operations like opening and closing windows, switching between applications, and using paint software. He positions Windows as a revolutionary advancement in personal computing, promising a more intuitive and efficient working experience.
Commenters on Hacker News reacted to the Windows 1.0 video with a mix of nostalgia and amusement. Several noted the awkwardness of early software demos, particularly Ballmer's forced enthusiasm and the clunky interface. Some reminisced about their own experiences with early versions of Windows, while others pointed out the historical significance of the moment and how far personal computing has come. A few highlighted the surprisingly high system requirements for the time, and the relative affordability compared to other graphical interfaces like the Macintosh. There was some debate about the actual usefulness of Windows 1.0 and whether it was truly a "killer app." Overall, the comments reflected a sense of appreciation for the historical context of the video and the progress made since then.
Summary of Comments ( 2 )
https://news.ycombinator.com/item?id=44021191
Several commenters on Hacker News praised RISC OS's GUI for its speed, simplicity, and innovative features like the icon bar and context menus. Some noted its influence on other operating systems, particularly in the mobile space. Others discussed its unique cooperative multitasking model and its drawbacks compared to preemptive multitasking. A few users shared personal anecdotes about using RISC OS, highlighting its appeal to hobbyists and its dedicated community. Some lamented the lack of wider adoption and speculated about its potential had it been open-sourced earlier. The discussion also touched upon the challenges of porting it to modern hardware and the limitations of its single-user design.
The Hacker News post titled "The RISC OS GUI" has generated a moderate number of comments, mostly revolving around the unique design choices of RISC OS, its performance, and comparisons to other operating systems.
Several commenters discuss the distinctive "click and drag" interface for selecting text and other elements, contrasting it with the more common double-click approach. Some appreciate its efficiency once mastered, while others find it counterintuitive. One commenter elaborates on how this mechanism extends to window management, where dragging a window's title bar moves it, and dragging its edges resizes it, all without dedicated buttons. This unconventional approach sparks debate on its usability and learnability.
The performance of RISC OS is another prominent topic. Commenters highlight its speed and responsiveness, often attributed to its tight integration with the underlying ARM hardware and efficient coding. One commenter fondly recalls its impressive performance even on older, less powerful hardware. Another speculates that the design choices, such as the cooperative multitasking model, contribute to its perceived snappiness.
Comparisons to other operating systems are also frequent. Some commenters liken RISC OS's philosophy to that of earlier versions of MacOS, pre-OSX, with its focus on simplicity and direct manipulation. Others mention BeOS as another example of an innovative operating system with unique GUI paradigms. The discussion also touches on how RISC OS deviates from the dominant Windows/MacOS/Linux desktop environments, prompting reflections on alternative design philosophies.
A few comments delve into the technical underpinnings of RISC OS. One commenter notes the absence of memory protection in older versions, which contributed to its speed but also made it less robust. Another explains the cooperative multitasking model, where applications voluntarily relinquish control to the system, contrasting it with the preemptive multitasking found in most modern operating systems.
There's also a discussion on the accessibility of RISC OS today, with some commenters providing links to emulators and resources for those interested in trying it out. A recurring theme is the nostalgic appreciation for RISC OS among those who used it in the past, often accompanied by lamentations about its decline in popularity.
While no single comment dominates the discussion, the collective conversation paints a picture of RISC OS as a unique and intriguing operating system, praised for its speed and unconventional interface, while acknowledged for its limitations and departure from mainstream design. The comments offer a blend of technical insights, personal anecdotes, and comparative analyses, providing a multi-faceted perspective on this less-known operating system.