{
  "id": 11904098,
  "title": "Revive Raskin's 3 laws of software with humane work that considers a dev's duty of care",
  "url": "https://urgent.news/2026/10/04/revive-raskins-3-laws-of-software-with-humane-work-that-considers-a",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-04T10:30:00.000Z",
  "source": {
    "name": "The Register Science",
    "slug": "the-register-science",
    "url": "https://www.theregister.com/software/2026/10/04/revive-raskins-3-laws-of-software-with-humane-work-that-considers-a-devs-duty-of-care/5300539"
  },
  "original_language": "en",
  "account": "In 1942, Isaac Asimov established three laws of robotics, and 58 years later, Jef Raskin added three laws of human-computer interface design. Despite the passage of time and advancements in technology, these laws have not been surpassed. While Linux has made Unix accessible to the masses in the last three decades, the open-source software world has yet to fully comprehend these principles. Conversely, the proprietary software industry appears to have forgotten the foundational rules.\n\nMarcin Wichary's recent blog post, \"They had no concept of a duty of care to their users,\" highlights this issue as an example of FOSS scofflaws. Wichary references CHERI Project researcher David Chisnall, who recently attempted to switch from Vim to NeoVim. Chisnall, a long-term Vim user, experienced significant issues when switching, as NeoVim overwrote Vim's persistent undo file, which had recorded changes for over a decade. Chisnall acknowledges that a warning was present, but he expected NeoVim's undo system to be safe. He emphasizes that Vim's undo feature has maintained stability across major version upgrades for approximately 20 years.\n\nChisnall's citation of Raskin's first law illustrates the importance of maintaining user data integrity. Raskin's first law states that a program must not harm a user's data or allow that data to come to harm through inaction. This principle underscores the responsibility of software developers to ensure that their applications do not compromise user information, even during system crashes or file reopening. Wichary expands on this by incorporating all three of Raskin's laws, emphasizing the need for humane, user-friendly interfaces.\n\nAsimov's original three laws were introduced to prevent the creation of \"killer-robot\" stories by setting clear boundaries for robot behavior. Similarly, Raskin's three laws aim to establish a framework for designing user interfaces that prioritize user safety, efficiency, and consider human frailties. Despite Raskin's contributions, the FOSS community has often been criticized for neglecting these principles. As a result, some FOSS developers have faced backlash for not adequately addressing user concerns, particularly regarding data integrity and system stability.\n\nThe debate surrounding Vim and NeoVim serves as a prime example of the consequences when developers fail to adhere to Raskin's laws. Vim's persistence of undo history across major updates demonstrates the potential for software to function seamlessly over time, even in the face of version changes. However, NeoVim's decision to overwrite Vim's undo file without warning highlights the risks associated with abrupt changes that disrupt user workflow and data integrity. Such actions not only violate Raskin's first law but also undermine the trust users place in software applications.\n\nIn the broader context of software design, the emphasis on user-centric, simple, and hand-coded solutions offers a refreshing perspective. Emulating an original Macintosh on a low-cost chip exemplifies the potential for innovation in the realm of user-friendly, accessible software. By focusing on ease of use and minimal complexity, developers can create tools that prioritize the user's needs first, leading to more robust and reliable applications. As the industry continues to evolve, it is crucial to revisit and uphold the foundational principles laid out by Asimov and Raskin to ensure that software remains a force for positive change rather than a source of frustration and harm.",
  "summary": "All this, and angry NeoVim users",
  "key_points": [
    "Marcin Wichary's blog post highlights FOSS scofflaws ignoring Raskin's laws.",
    "David Chisnall's Vim to NeoVim switch illustrates importance of data integrity.",
    "Raskin's first law emphasizes maintaining user data safety during system changes."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 2,
    "also_reported_by": [
      {
        "outlet": "The Register",
        "title": "Revive Raskin's 3 laws of software with humane work that considers a dev's duty of care",
        "url": "https://urgent.news/2026/10/04/revive-raskins-3-laws-of-software-with-humane-work-that-considers-a-11906217",
        "published": "2026-10-04T10:30:00.000Z"
      }
    ]
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}