DEV TOOLS Signal 392
The early days of UNIX development in the UK detailed by George Coulouris
↗
Illustration only Photo by Tyler on Unsplash
Comments
This account provides insights into the genesis of UNIX tools like 'em', which influenced later editors like 'vi'. Understanding this history can help engineers appreciate the evolution of software development practices. It highlights the challenges of optimizing software for different environments, a relevant concern in today's development.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
George Coulouris developed 'em', an early text editor for UNIX, in 1975.
Concerns about performance in a multi-user environment initially limited 'em's adoption.
Bill Joy later adapted 'em into 'ex' and 'vi', showing the evolution of user-friendly text editors.
THE READ
What the cluster adds up to.
George Coulouris's development of 'em' in 1975 marked a significant step in UNIX's usability, as it aimed to provide immediate feedback for text editing. This innovation came from his need to exploit new terminal technology effectively, illustrating how user needs can drive software development.
Despite its potential, 'em' faced criticism for its resource demands, particularly the overhead of running in 'raw' mode. This highlights a common tension in software engineering between innovative features and system performance, especially in larger multi-user environments.
The eventual adoption of 'em' by Bill Joy, leading to the development of 'ex' and 'vi', demonstrates how initial ideas can evolve and become integral to a system. It reflects the iterative nature of software development, where early concepts can lay the groundwork for widely-used tools.
Coulouris's experience indicates the importance of user feedback in shaping software design. The transition from 'em' to 'vi' underscores how even a seemingly flawed concept can be refined into something valuable through collaboration and adaptation.
Overall, this historical account is a reminder for engineers of the importance of understanding both user needs and system limitations when developing new tools, as well as the potential impact of innovation on future software practices.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER