new standards

Designing new standards.
New OS architectures, protocols for file-sharing and file handling and program-file interaction, and how programs interconnect in general.
Current software architecture is very old and very broken.

Some goals:
* config files as turing-complete computational units that can interact with other stuff
* programs have a universal way of receiving commands for things to do as well as sending them back out, so everything is automatable
* within a system, the OS distributes ressources, and programs negotiate and consent or reject permission contract with each other for what they can do
* more ideas like this

Is anyone doing stuff like this ?

dicks out for Harambe

>>1

* config files as turing-complete computational units that can interact with other stuff

congratulations, you just reinvented every single program that uses scripts (Scheme, Lua, TCL) as configuration; provable, automatically analyzable, Turing-incomplete config with well-defined syntax and semantics is the way to go (see: Dhall)

* programs have a universal way of receiving commands for things to do as well as sending them back out, so everything is automatable

congratulations, you just reinvented stdin and stdout, or maybe message passing

* within a system, the OS distributes ressources

congratulations, you just reinvented a scheduler

programs negotiate and consent or reject permission contract with each other for what they can do

congratulations, you just reinvented mandatory access control

in conclusion: your're are an anus

Take the single task operating system redpill.

Real-time autonomous systems is for robots

robo raper

TempleOS does not seem to adhere to your standards, therefore your standards are wrong.

Congratulations, you just reinvented systemd.