Project ideas from Hacker News discussions.

The Unix executable as a Smalltalk method (2025) [video]

📝 Discussion Summary (Click to expand)

1. The filesystem as an object hierarchy

Directories are treated as objects that contain class‑ and instance‑files, with path files coordinating inheritance and method lookup. This makes the shell itself a dynamic object graph.

“Directories are objects. Files are interfaces. The filesystem IS the object graph.” – Selfish COM

The approach was formalised in a patent that maps class hierarchies onto nested directories, allowing shell scripts to inherit behaviour just like normal OOP classes. > “A method and apparatus for implementing a class hierarchy of objects in a hierarchical file system… The class hierarchy comprises a root class… Each class is implemented with a hierarchy of class directories and class files… Inheritance is achieved by controlling the invocation of class methods, using these path files.” – US 5187786A (cited by DonHopkins)


2. PostScript‑based object orientation (the “linguistic motherboard”)

The stack‑oriented nature of PostScript makes it a natural substrate for Smalltalk‑style objects, a insight that powered NeWS and later projects like MOOLLM.

“PostScript is a linguistic ‘mother board’, which has ‘slots’ for several ‘cards’… The first card we built was a graphics card. We're considering other cards…” – John Warnock (as recounted by Owen Densmore)

Owen Densmore explicitly described how dictionaries act as class definitions and how the stack implements inheritance:

“Push a class dictionary onto the stack; method lookup walks the stack (multiple inheritance).” – Owen Densmore


3. Cross‑generational influence of OOP in NeWS and early GUIs

The NeWS toolkit demonstrated that UI components can be programmed directly in PostScript, enabling runtime inheritance and novel features such as pie‑menus that users could customise.

“Only the diehards want to develop applications using basic window system facilities. The preferred approach is a higher‑level ‘toolkit’… Experience with current toolkits shows the need for an object‑oriented interface to these components.” – David Rosenthal

The same OOP concepts that drove NeWS also inspired early work on the Unix shell, linking window‑system objects to shell scripting and later to LLM‑oriented architectures.

“Objects & Methods… We organized objects in the window system in a class hierarchy with inheritance… This allowed Don Hopkins to implement pie menus… This was such fun that Owen Densmore and I used the same technique to implement object‑oriented programming for the Unix shell.” – David Rosenthal


🚀 Project Ideas

Generating project ideas…

ObjectFS Shell

Summary

  • A shell extension that treats directories as first‑class objects with class hierarchies, enabling Smalltalk‑style inheritance and method lookup directly in the filesystem.
  • Provides a clean, scriptable way to organize complex workflows without external OOP frameworks.

Details

Key Value
Target Audience Shell script developers, DevOps engineers, data scientists
Core Feature Hierarchical class directories where each directory holds method files; path files encode inheritance and method resolution
Tech Stack Python (FUSE layer), Rust (performance‑critical parts), Bash/zsh completion scripts
Difficulty Medium
Monetization Hobby

Notes

  • HN users repeatedly lament the lack of a “real” object system in *nix shells – this directly addresses that frustration.
  • The design mirrors the patented filesystem‑as‑object hierarchy, giving practical utility to the 30‑year‑old concept.
  • Could be packaged as a plug‑in for existing shells (e.g., fish, zsh) and distributed as open‑source CLI tool.

NeWS UI Builder

Summary

  • A visual designer that lets users create UI components as YAML “agent” definitions and compile them into PostScript objects for rendering.
  • Eliminates the need to hand‑write PostScript code while preserving the OOP and inheritance advantages of NeWS.

Details

Key Value
Target Audience Retro UI developers, open‑source graphics hobbyists, educators teaching graphics/computer graphics
Core Feature YAML‑based component definitions with method inheritance; automatic generation of PostScript code executed via Ghostscript
Tech Stack Node.js front‑end, Python backend (YAML parsing + Ghostscript invocation), Docker for sandboxed rendering
Difficulty High
Monetization Hobby

Notes

  • Commenters talk about “PostScript as a linguistic motherboard” and desire modern UI toolkits – this bridges that gap.
  • Provides a tangible way to experiment with the historic NeWS object‑oriented UI concepts on contemporary hardware.
  • Could be released as a free desktop app with optional paid plug‑ins for advanced animation features.

AgentDirectory Platform

Summary

  • A cloud‑native service that stores LLM‑driven agents as versioned directory objects, exposing a filesystem‑style API for creation, cloning, and querying.
  • Solves the pain point of losing persistent agent state across sessions and enables reproducible AI pipelines.

Details

Key Value
Target Audience AI researchers, LLM engineers, enterprise workflow designers
Core Feature Persistent agent directories with immutable state snapshots; REST‑ful API that mirrors file operations (mkdir, cp, rm) for agent management
Tech Stack FastAPI (Python), PostgreSQL for metadata, Redis for caching, Docker Compose for deployment
Difficulty High
Monetization Revenue-ready: SaaS with tiered pricing – $0.01 per agent‑hour storage + $0.05 per API‑call

Notes

  • HN discussion about “Selfish COM” and “directory‑as‑object” shows appetite for filesystem‑level agent models.
  • Aligns with the patented class‑hierarchy‑in‑filesystem idea, giving it a modern AI twist.
  • Offers clear commercial potential: hosted agent versioning, audit trails, and collaboration features for teams.

Read Later