https://github.com/Symatem/Documentation

https://github.com/Symatem/Documentation

documentation ideation reasoning

Last synced: about 1 month ago
JSON representation

• Host: GitHub
• URL: https://github.com/Symatem/Documentation
• Owner: Symatem
• Created: 2017-08-21T16:41:24.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2020-08-19T09:54:14.000Z (over 4 years ago)
• Last Synced: 2024-08-01T12:37:22.296Z (4 months ago)
• Topics: documentation, ideation, reasoning
• Homepage:
• Size: 60.5 KB
• Stars: 7
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

• awesome-starred - Symatem/Documentation - (documentation)

README

        
# SYMbol relAtion sysTEM (Symatem)

## What is this Project About?

This project is a different approach to many practical parts of software development.

If you give it a try, you will find out soon, that even though some things are familiar others are completely alien to you.

I recommend [this WBW Post](http://waitbutwhy.com/2015/11/the-cook-and-the-chef-musks-secret-sauce.html) about thinking differently in general.

An analogy I came to like, even though it is inspired by the heavily overused quote attributed to Henry Ford, is the following:

Imagine we would still live in a world of horses.

If I were to talk about how I think I can revolutionize the transport system

most people would expect some sort of genetically modified horses to run faster or something alike.

When I talk about my idea of a car people get interested and want to know more details.

And when I proceed to talk about the components and subsystems of the car, I get questions like this:

"Where does this transmission-thingy fit into my horse and how is that supposed to make it faster?"

So as hybrids of cars and horses obviously don't make any sense,

a tight integration of this project and most other software makes not so much sense either.

In fact I want to keep it standing for itself and only use a few popular technologies as a launch pad

similar to cars and horses sharing the same roads in the early days.

And before you get too hyped up about all the things you might read here,

keep in mind that the first cars were merely toys of their inventors and nothing like the ones we drive (or may soon drive us) today.

So even if I succeed in constructing and presenting my prototype system,

we still have a long journey ahead of us to make it really useful.

## Architecture

I tried to break things down to their basic elements and rearrange them in a useful way regardless of how most others are doing them nowadays.

The goal is to explore the possibility and develop a consistent system / framework uniting all of these components:

- Processing

    - [Programming](Processing/Programming.md)

    - [Compiler](Processing/Compiler.md)

    - [Concurrency](Processing/Concurrency.md)

    - [Standard Library](Processing/StandardLibrary.md)

    - [Runtime Environment](Processing/RuntimeEnvironment.md)

- Transport (Encode / Decode)

    - Transport in time: Storage (Write / Read)

    - Transport in space: Transmission (Send / Receive)

    - [Ontology Engine](Transport/Ontology.md) / Database / File System

        - [Internal Format](Transport/InternalFormat.md)

        - [External Format](Transport/ExternalFormat.md)

    - [Encodings](Transport/Encodings.md)

    - [Version Control](Transport/VersionControl.md)

    - Distribution

- Toolchain

    - [User Interface](Toolchain/UserInterface.md)