Visopsys: OS maintained by a single developer since 1997 (visopsys.org)

Article summary

The article discusses Visopsys, an operating system that has been maintained by a single developer since 1997 and is still in version 0.9. The OS has its own unique features and design. The article also touches on the topic of versioning and how different systems approach it. The discussion around Visopsys and versioning sparks a debate about the best practices for software development and user experience.

Main themes

• Visopsys OS
• Versioning systems
• Software development
• User experience
• API design
• Operating system design

What commenters say

• The use of semantic versioning is not necessary for all types of software and can be overly complex for some systems.
• Versioning schemes should be tailored to the specific needs of the software and its users, rather than following a one-size-fits-all approach.
• Some users prefer a simple and minimalistic user interface, while others value more detailed and expressive feedback, such as the volume indicator in iOS.
• The removal of certain features, like the volume indicator in iOS, can be seen as arbitrary or deliberate, and may not always align with user needs or expectations.
• Different versioning schemes, such as calendar versioning, can be more effective for certain types of software, like user-facing applications.
• The distinction between API versioning and user versioning is important, as they serve different purposes and require different approaches.
• Some argue that semantic versioning is only relevant for APIs and not for user-facing software, while others see it as a useful tool for communicating changes and backwards compatibility.
• The design of an operating system, including its versioning scheme, should prioritize user needs and expectations, rather than solely focusing on technical considerations.