Roadmap #3
Description
The core fundamentals of simplicity
We should aim for simplicity because simplicity is a prerequisite for reliability.
This means if your software is not change able by a outside contributor in less then 1 day to fix his problems then your software is easy sayed not simple.
Simple is often erroneously mistaken for easy.
"Easy" means "to be at hand", "to be approachable". "Simple" is the opposite of "complex" which means "being intertwined", "being tied together". Simple != easy.
What matters in software is:
The answers to these questions is what matters in writing software not the look and feel of the experience writing the code or the cultural implications of it.
does the software do what is supposed to do?
Is it of high quality?
Can we rely on it?
Can problems be fixed along the way?
Can requirements change over time?
The benefits of simplicity are:
ease of understanding, ease of change, ease of debugging, flexibility, modules are pure functions that are recomposeable into a component. The mantra is alwas composition over inharitance. Never create a class or structure for data always view the data in your way.
Complex constructs:
State, Object, Methods, Syntax, Inheritance, Switch/matching, Vars, Imperative loops, Actors, ORM, Conditionals.
Simple constructs:
Const, Functions, Data, Polymorphism, Managed refs, Streams, Declarative data manipulation, Rules, Consistency.
Build simple systems by:
Abstracting - design by answering questions related to what, who, when, where, why, and how. Choosing constructs that generate simple artifacts like modules that do not reference other modules without a unified resolver method that produces static in memory references... Simplify by encapsulation via composition of functions and streams.
Fork injection pattern
as they like content security.
we can build a fork out of the github integration via injection of our own repo into them
https://stackblitz.com/github/unlicense-code/web-modules
Design
| What | who | when | how |
|---|---|---|---|
| serviceWorker Deployment | entrypoint html domain context | first visit | html code snippet |
| booting monaco editor on 3th party subdomain | entrypoint html domain context | after serviceWorker Deployment | via iframe |
| offer github sso and api | 3th party subdomain | bootload 3th party subdomain | after monaco |