hackslash dot org

Show HN: A new native app for 20 year old OS X

Posted: 2025-01-24 00:46:55

Chad Bibler has created Uppercut, a new native application specifically designed for older PowerPC Macs running Mac OS X 10.4 (Tiger) and 10.5 (Leopard). Focusing on modern web browsing, Uppercut uses WebKit2 to provide a more secure and up-to-date browsing experience on these legacy systems. While acknowledging the limitations of the aging hardware, the app aims to offer a viable way to access current websites on these vintage machines.

Chad Bibler has unveiled a newly developed native application specifically designed for the venerable Mac OS X operating system, an impressive feat considering its age of two decades. This application, christened "Uppercut," aims to address a specific, yet persistent, irritation for users of older Mac OS X versions: the inability to easily force quit frozen or unresponsive applications. While newer macOS iterations offer a refined and readily accessible "Force Quit" dialogue, earlier versions of OS X lacked this convenient functionality, often necessitating a full system restart, a disruptive solution to a relatively minor problem.

Uppercut offers a streamlined and efficient solution to this historical shortcoming. It presents a compact, unobtrusive window that displays a list of all currently running applications. Users can then select the offending, non-responsive application from this list and, with a simple click of a button or a keyboard shortcut, forcibly terminate the selected process. This allows users to regain control of their system without resorting to the more drastic measure of a full reboot, preserving their work and avoiding unnecessary downtime.

The application's native design ensures seamless integration with the classic Mac OS X aesthetic. It leverages the familiar interface elements and design principles of the era, creating a cohesive and user-friendly experience. Furthermore, the developer has made Uppercut available as a free and open-source project, encouraging community involvement and allowing users to examine, modify, and contribute to the application's continued development. This commitment to open-source principles aligns with the spirit of early Mac OS X development and fosters a collaborative environment for preserving and enhancing the usability of this legacy operating system. In essence, Uppercut provides a modern solution to a long-standing problem for users clinging to, or appreciating, the classic charm of Mac OS X.

Summary of Comments ( 3 )
https://news.ycombinator.com/item?id=42809518

HN commenters generally praised the Uppercut app for its clean design and focus on essential features, seeing it as a refreshing alternative to overly complex modern software. Some questioned the long-term viability of supporting such an old OS, while others reminisced about the simplicity of older macOS versions. Several users suggested potential improvements, including adding syntax highlighting for more languages and incorporating Git integration. The developer responded to several comments, clarifying design choices and acknowledging feature requests. A few commenters expressed concerns about the app's name potentially confusing it with the existing Uppercut vector graphics editor.

The Hacker News post "Show HN: A new native app for 20 year old OS X" generated several comments discussing the showcased app, Uppercut, a menu bar application for macOS.

Many commenters expressed appreciation for the app's clean and simple design, particularly praising its adherence to classic macOS UI principles. They found it refreshing to see a new app that respects the older aesthetic and avoids the trend towards overly complex or "modernized" interfaces. Several users specifically mentioned enjoying the use of native UI elements and the avoidance of Electron or other cross-platform frameworks.

The developer's decision to target older macOS versions was also a point of discussion. While some questioned the practicality of supporting such outdated systems, others praised the commitment to maintaining compatibility for users who might be running older hardware or prefer the classic OS experience. This sparked a broader conversation about software longevity, the challenges of supporting legacy systems, and the value of maintaining backwards compatibility.

Some commenters inquired about specific features and functionalities, such as keyboard shortcuts, customization options, and potential future additions. The developer actively engaged with these comments, responding to questions and providing insights into the app's design choices and development roadmap.

A few users offered constructive criticism, suggesting improvements like better integration with existing menu bar utilities and more robust error handling. These suggestions were generally well-received by the developer and other commenters.

There was also some discussion around the choice of programming language (Swift) and the developer's experience building the app. The developer's willingness to share their process and engage with the community was appreciated by many.

Overall, the comments were largely positive, reflecting a general appreciation for the app's design, functionality, and the developer's commitment to the macOS platform. The discussion also touched upon broader themes of software development, UI/UX design, and the challenges of supporting legacy systems.

Mac Mini G4 – The best « classic » Macintosh for retro-gaming?

permalink

Posted: 2025-01-12 15:53:02

The Mac Mini G4 strikes a sweet spot for classic Mac gaming, balancing performance, affordability, and size. Its PowerPC G4 processor handles early 2000s Mac OS X games well, including some Classic environment titles. While not as powerful as the Power Mac G5, its smaller footprint and lower cost make it more practical. The option for an internal optical drive is beneficial for playing original game discs, and it supports various controllers. Though not perfect due to limitations with certain later-era games and the eventual demise of Rosetta, the Mini G4 remains an excellent entry point for exploring the older Macintosh gaming library.

Xavier Toffoli's blog post, "Mac Mini G4 – The best « classic » Macintosh for retro-gaming?", explores the merits of the PowerPC G4-based Mac Mini as a platform for playing older video games, particularly those designed for classic Mac OS and early Intel-based Macs. Toffoli frames his argument by acknowledging the existing popularity of older Macintosh models for retro gaming, such as the iMac G3 and Power Macintosh G3/G4, but posits that the Mac Mini G4 offers a compelling combination of factors that distinguish it as a potentially superior choice.

He highlights the Mac Mini G4's relatively compact size, making it easily transportable and less demanding of desk space compared to its bulkier predecessors. This portability, combined with its relatively low power consumption, contributes to its practicality as a retro gaming machine. Toffoli emphasizes the machine's quiet operation, a significant advantage over the often noisy fans found in older Macs, allowing for a more immersive and less distracting gaming experience.

The author delves into the technical specifications of the Mac Mini G4, explaining how its PowerPC G4 processor, coupled with the capabilities of Mac OS 9 and early versions of Mac OS X, allows for compatibility with a wide range of classic Macintosh games. He notes the system's ability to run both Classic environment software (older Mac OS applications) within OS X and natively boot into OS 9, offering flexibility for different gaming needs. Furthermore, he points out that the Mac Mini G4 can also run early Intel-based Mac games through Rosetta, Apple's software layer for PowerPC emulation on Intel Macs, expanding the potential library of playable titles. This bridging of the PowerPC and Intel eras contributes to the machine's versatility.

Toffoli acknowledges some limitations, such as the Mac Mini G4's integrated graphics, which may struggle with more demanding 3D games designed for later Mac models. He also discusses the potential need for upgrades, such as increasing RAM or installing a larger hard drive, to optimize performance and storage capacity for a larger game library. Despite these limitations, he concludes that the Mac Mini G4, with its balance of performance, compact design, quiet operation, and software compatibility, represents a compelling and arguably optimal choice for enthusiasts seeking a dedicated machine for experiencing the rich history of Macintosh gaming. He underscores the machine's ability to offer a satisfying retro gaming experience across a spectrum of titles, from older Mac OS classics to early Intel-era releases.

Summary of Comments ( 111 )
https://news.ycombinator.com/item?id=42674385

Hacker News users generally agree with the article's premise that the Mac Mini G4 is a good choice for classic Mac gaming. Several commenters praise its relatively compact size, affordability, and ability to run OS 9 and early OS X, covering a wide range of game titles. Some highlight the ease of upgrading the RAM and hard drive. However, some dissent arises regarding its gaming capabilities compared to earlier PowerPC Macs like the G3 or G4 towers, suggesting they offer superior performance for certain games. Others point to the lack of AGP graphics as a limitation for some titles. The discussion also touches on alternative emulation methods using SheepShaver or Basilisk II, though many prefer the native experience offered by the Mini. Several commenters also share personal anecdotes about their experiences with the Mac Mini G4 and other retro Macs.

The Hacker News post "Mac Mini G4 – The best « classic » Macintosh for retrogaming?" sparked a modest discussion with a few interesting points raised.

One commenter highlights the Mac Mini G4's advantages for retro gaming, specifically its compact size, relatively powerful PowerPC G4 processor, ability to boot into both Mac OS 9 and early versions of OS X, and support for classic Mac games that often struggle on later Intel-based Macs. They also mention the ease of upgrading the RAM and hard drive. This commenter positions the Mini as a good compromise, lacking the expandability of a full tower G4 but offering a more practical and space-saving solution.

Another commenter agrees with the original post's sentiment, emphasizing the Mac Mini G4's balance of performance and affordability, calling it the "sweet spot" for classic Mac gaming. They further note the benefit of its official support for Tiger, which allows for running emulators for other retro systems.

A different commenter expresses nostalgia for this era of Apple hardware, recounting their positive experience using a PowerBook G4. While not directly related to gaming, this comment adds to the overall sentiment of appreciation for the G4 era.

Another contributor points out the potential challenge of finding suitable displays for older Macs, as many modern monitors lack the necessary connections. They suggest exploring solutions like DVI to HDMI converters or specifically seeking out older displays with DVI or VGA inputs. This practical consideration provides valuable context for anyone looking to set up a retro gaming system with a Mac Mini G4.

Finally, a commenter mentions the iBook G4 as another viable, and often cheaper, alternative for retro gaming, although acknowledging its lower performance compared to the Mini.

While the discussion thread is not extensive, it offers valuable insights into the advantages and considerations of using a Mac Mini G4 for retro gaming, touching on aspects like performance, practicality, compatibility, and alternative options.

DOS APPEND

permalink

Posted: 2024-12-20 21:04:59

DOS APPEND, similar to the PATH command, allows you to specify directories where DOS should search for data files, not just executable files. This lets programs access data in various locations without needing full path specifications. It supports both drive letters and network paths, and offers options to search appended directories before the current directory or to treat appended directories as subdirectories of the current one. APPEND also provides commands to display the current appended directories and to remove them. This expands the functionality beyond the simple executable search of PATH, making data access more flexible.

The blog post "DOS APPEND" from the OS/2 Museum meticulously details the functionality and nuances of the APPEND command in various DOS versions, primarily focusing on its evolution and differences compared to the PATH command. APPEND, much like PATH, allows programs to access data files located in directories other than their current working directory. However, while PATH focuses on executable files, APPEND extends this capability to data files, specified by various file extensions.

The article begins by explaining the initial purpose of APPEND in DOS 3.3, highlighting its ability to search specified directories for data files when a program attempts to open a file not found in the current directory. This eliminates the need for programs to explicitly handle path information for data files. The post then traces the development of APPEND through later DOS versions, including DOS 3.31, where a significant bug related to networked drives was addressed.

A key distinction between APPEND and PATH is elaborated upon: PATH affects only the search for executable files (.COM, .EXE, and .BAT), while APPEND pertains to data files with extensions specified by the user. This difference is crucial for understanding their respective roles within the DOS environment.

The blog post further delves into the various ways APPEND can be used, outlining the command-line switches and their effects. These switches include /E, which loads the appended directories into an environment variable, /PATH:ON, which enables searching the appended directories even when a full path is provided for a file, and /PATH:OFF, which disables this behavior. The post also explains the use of /X, which extends the functionality of APPEND to affect the EXEC function calls, thus influencing child processes.

The evolution of APPEND continues to be discussed, noting the removal of the problematic /X:ON and /X:OFF switches in later versions due to their instability. The article also touches upon the differences in behavior between APPEND in MS-DOS/PC DOS and DR DOS, particularly concerning the handling of the ; delimiter in the APPEND list and the search order when multiple directories are specified.

Finally, the post concludes by briefly discussing the persistence of APPEND in later Windows versions for compatibility, even though its utility diminishes in these more advanced operating systems with their more sophisticated file management capabilities. The article thoroughly explores the intricacies and historical context of the APPEND command, offering a comprehensive understanding of its functionality and its place within the broader DOS ecosystem.

Summary of Comments ( 56 )
https://news.ycombinator.com/item?id=42475011

Hacker News users discuss the DOS APPEND command, primarily focusing on its obscure nature and surprising functionality. Several commenters recall struggling with APPEND's unexpected behavior, particularly its ability to make files appear in directories where they don't physically exist. The discussion highlights the command's similarity to environment variables like PATH and LD_LIBRARY_PATH, with one user pointing out that it effectively extends the file search path for specific programs. Some comments mention the utility of APPEND for accessing data files across drives or directories without hardcoding paths, while others express their preference for more modern solutions. The overall sentiment suggests APPEND was a powerful but complex tool, often misunderstood and potentially problematic.

The Hacker News post titled "DOS APPEND" with the link https://www.os2museum.com/wp/dos-append/ has several comments discussing the utility of the APPEND command in DOS and OS/2, as well as its quirks and comparisons to other operating systems.

One commenter recalls using APPEND frequently and finding it incredibly useful, particularly for accessing data files located in different directories without having to constantly change directories or use full paths. They highlight the convenience it offered in a time before sophisticated development environments and integrated development environments (IDEs).

Another commenter draws a parallel between APPEND and the modern concept of environment variables like $PATH in Unix-like systems, which serve a similar purpose of specifying locations where the system should search for executables. They also touch on how APPEND differed slightly in OS/2, specifically regarding the handling of data files versus executables.

Further discussion revolves around the intricacies of APPEND's behavior. One comment explains how APPEND didn't just search the appended directories but actually made them appear as if they were part of the current directory, creating a virtualized directory structure. This led to some confusion and unexpected behavior in certain situations, especially with programs that relied on obtaining the current working directory.

One user recounts experiences with the complexities of managing multiple directories and files in early versions of Turbo Pascal, illustrating the context where a tool like APPEND would have been valuable. This comment also highlights the limited tooling available at the time, emphasizing the appeal of features like APPEND for streamlining development workflows.

Someone points out the potential for conflicts and unexpected results when using APPEND with programs that create files in the current directory. They suggest that APPEND's behavior could lead to files being inadvertently created in a directory different from the intended one, depending on how the program handled relative paths.

The security implications of APPEND are also addressed, with a comment mentioning the risks associated with accidentally executing programs from untrusted directories added to the APPEND path. This highlights the potential security vulnerabilities that could arise from misuse or improper configuration of the command.

Finally, there's a mention of a similar feature called apppath in the REXX language, further illustrating the cross-platform desire for this kind of directory management functionality.

Overall, the comments paint a picture of APPEND as a powerful but somewhat quirky tool that provided a valuable solution to directory management challenges in the DOS/OS/2 era, while also introducing potential pitfalls that required careful consideration. The discussion showcases how APPEND reflected the computing landscape of the time and how its functionality foreshadowed concepts that are commonplace in modern operating systems.

Ascending Mount FujiNet

permalink

Posted: 2024-12-18 02:27:24

This blog post details the author's successful implementation of a FujiNet network adapter for a Tandy Color Computer 3. After encountering initial difficulties with a pre-assembled device, they opted to build their own using a kit. This involved careful soldering and troubleshooting, particularly with the SD card interface. Ultimately, they achieved a stable connection, enabling them to access a virtual floppy drive and remotely transfer files to the CoCo 3 via a local network, significantly enhancing its capabilities. The author emphasizes the improved speed and convenience compared to traditional floppy disks and expresses satisfaction with the FujiNet's performance.

This meticulously detailed blog post, "Ascending Mount FujiNet," chronicles the author's multifaceted journey to achieve robust and reliable networking capabilities for their Tandy Color Computer 3. The narrative begins by outlining the existing limitations of networking solutions for this vintage hardware, primarily focusing on the speed constraints of the serial port. The author then introduces the FujiNet project, an ambitious endeavor to implement a modern network interface for the CoCo 3 utilizing an ESP32 microcontroller. This endeavor isn't merely about connecting the machine to the internet; it involves crafting a sophisticated system that emulates legacy peripherals like hard drives and floppy drives, streamlining the process of transferring files and interacting with the retro hardware.

The author meticulously documents their methodical exploration of various hardware and software components required for the FujiNet implementation. They delve into the specifics of setting up the ESP32, configuring the necessary software, and integrating it with the CoCo 3. The challenges encountered are described in detail, including addressing conflicts with memory addresses and navigating the complexities of interrupt handling. The narrative emphasizes the iterative nature of the process, highlighting the adjustments made to hardware configurations and software parameters to overcome obstacles and optimize performance.

A significant portion of the post is dedicated to elucidating the intricacies of network booting. The author explains the process of configuring the CoCo 3 to boot from the network, leveraging the capabilities of the FujiNet system. They discuss the importance of network boot ROMs and the modifications required to accommodate the enhanced functionality offered by FujiNet. The post also delves into the mechanisms of loading different operating systems and disk images remotely, showcasing the versatility of the network booting setup.

Furthermore, the author explores the integration of specific software, such as the RS-DOS operating system, demonstrating how FujiNet seamlessly bridges the gap between the vintage hardware and modern network resources. The ability to access files stored on a network share as if they were local drives is highlighted, underscoring the practical benefits of the FujiNet system for everyday use with the CoCo 3. The overall tone conveys the author's enthusiasm for retro computing and their meticulous approach to problem-solving, resulting in a comprehensive guide for others seeking to enhance their CoCo 3 experience with modern network connectivity. The post concludes with a sense of accomplishment and a glimpse into the future possibilities of the FujiNet project.

Summary of Comments ( 10 )
https://news.ycombinator.com/item?id=42447580

Several commenters on Hacker News express excitement about the FujiNet project, particularly its potential to simplify retro-computing networking. Some discuss their experiences with similar setups, highlighting the challenges of configuring vintage hardware for modern networks. The ability to use SD cards for virtual floppy disks and the promise of future features like BBS access and online multiplayer gaming generate considerable interest. Several users inquire about the hardware requirements and compatibility with various MSX models, demonstrating a practical interest in utilizing the technology. Some express nostalgia for older networking methods and debate the authenticity versus convenience trade-off. There's also discussion of alternative solutions like the MSX-DOS 2 TCP/IP driver, with comparisons to FujiNet's approach.

The Hacker News post "Ascending Mount FujiNet" discussing a blog post about the FujiNet networking device for 8-bit Atari systems generated several interesting comments.

One commenter expressed excitement about the project, highlighting the appeal of modernizing retro hardware without resorting to emulation. They appreciated the ability to use original hardware with modern conveniences. This sentiment was echoed by others who found the blend of old and new technology compelling.

Another commenter, identifying as the author of the blog post, clarified some technical details. They explained that while the current implementation uses ESP32 modules for Wi-Fi, the long-term goal is to develop a dedicated ASIC for a more integrated and potentially faster solution. This prompted a discussion about the feasibility and cost-effectiveness of ASIC development, with other commenters weighing in on the potential challenges and benefits.

There was also a discussion about the broader implications of the FujiNet project and its potential impact on the retro gaming community. Some commenters speculated on whether similar projects could be developed for other retro platforms, expanding the possibilities for online play and other modern features.

Several commenters shared their personal experiences with retro networking solutions, comparing FujiNet to other options and discussing the advantages and disadvantages of each. This led to a conversation about the challenges of preserving and maintaining retro hardware, and the importance of projects like FujiNet in keeping these systems accessible and enjoyable for future generations.

Finally, a few commenters focused on the technical aspects of the FujiNet implementation, discussing topics like network protocols, data transfer speeds, and the challenges of integrating modern networking technology with older hardware. These comments provided valuable insights into the complexities of the project and the ingenuity required to overcome them.

Stories with Tag vintage computing

Show HN: A new native app for 20 year old OS X

Summary of Comments ( 3 ) https://news.ycombinator.com/item?id=42809518

Mac Mini G4 – The best « classic » Macintosh for retro-gaming?

Summary of Comments ( 111 ) https://news.ycombinator.com/item?id=42674385

DOS APPEND

Summary of Comments ( 56 ) https://news.ycombinator.com/item?id=42475011

Ascending Mount FujiNet

Summary of Comments ( 10 ) https://news.ycombinator.com/item?id=42447580

Summary of Comments ( 3 )
https://news.ycombinator.com/item?id=42809518

Summary of Comments ( 111 )
https://news.ycombinator.com/item?id=42674385

Summary of Comments ( 56 )
https://news.ycombinator.com/item?id=42475011

Summary of Comments ( 10 )
https://news.ycombinator.com/item?id=42447580