bliss - LeFreq/Singularity GitHub Wiki

Imagine, wanting to create a new application. Normally such an idea doesn't occur to anybody but specialists called "programmers", and when it does they mentally prepare for a month or more of coding, testing, re-hashing, and testing some more. But in the future, people might get an idea for something the computer could do, and combine two objects here and there, and suddenly, with very little work, a whole new application is here.

That's what this OS will enable. Unix shells scripts made it linearly simpler (though most apps don't use shell simplicity). This is logarithmically simpler to remake an application, thanks to OOP and shell-like simplicity working together.

Or perhaps you're a programmer asked to change something in somebody's code. This kind of work gets $100/hr and many months of salary. But now, you can inspect the code, know what's going on because:

  1. it's documented, by necessity.
  2. it's compartmentalized, through the OSs object architecture, into single, modular objects (much like Unix commands)
  3. you can make sure your changes don't break anything because of built-in tests in the other's code.
  4. it's re-using objects you already know.
Now you're the hero, instead of the zero.
⚠️ **GitHub.com Fallback** ⚠️