From d24f193f49fe00eefc1ae5b46f555cc53e424ed5 Mon Sep 17 00:00:00 2001 From: fcrozatier Date: Fri, 7 Nov 2025 11:03:32 +0100 Subject: [PATCH 1/2] chore: improve readme --- README.md | 24 +++++++++++++++++++----- 1 file changed, 19 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index afb84f9..8b6c3e8 100644 --- a/README.md +++ b/README.md @@ -1,11 +1,25 @@ # F-Stack -Build modern web apps in a fun way and explore new frontiers +_Rethinking fullstack development_ -## [Functorial](./packages/functorial/README.md) +Here is my experimental stack. If you like when things fall neatly into place in a clean, coherent and holistic design then this is for you too. -The reactivity system. +## Values -## [Reflow](./packages/reflow/README.md) +1. The focus is on having **clean mental models** for every part of the stack. Which gives you a superpower: **understanding**. When you can reason clearly about your own application code then you're in a good, future proof, place. No magic. +2. I'm not after performance for it's own sake. It's JavaScript man, not Rust. As long as performance is good, I prefer clean, readable, maintainable code. I don't want to need 10 coffees to understand what I wrote. +3. I'm not chasing DX above all. Oftentimes too much comfort means "magic" solutions, where we loose track of what's going on. This quickly becomes un-debuggable and impossible to reason about. I don't trade long term understanding for immediate comfort. -The `html` template tag with common web mappings for attributes, listeners etc. +## Architecture + +The current pieces are (more to come): + +### [Functorial](./packages/functorial/README.md) + +A new `Proxy`-based reactivity system, that goes beyond Signals. More idiomatic. More granular. + +It's a structured way to declaratively interact with web API in a reactive manner + +### [Reflow](./packages/reflow/README.md) + +A minimal frontend framework powered by template tags and providing Functorial mappings to all common web APIs. From 97492a99f175581e0c6a33c573a9c1baa88ab50b Mon Sep 17 00:00:00 2001 From: fcrozatier Date: Fri, 7 Nov 2025 11:05:04 +0100 Subject: [PATCH 2/2] format --- README.md | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 8b6c3e8..f766f3f 100644 --- a/README.md +++ b/README.md @@ -2,13 +2,22 @@ _Rethinking fullstack development_ -Here is my experimental stack. If you like when things fall neatly into place in a clean, coherent and holistic design then this is for you too. +Here is my experimental stack. If you like when things fall neatly into place in +a clean, coherent and holistic design then this is for you too. ## Values -1. The focus is on having **clean mental models** for every part of the stack. Which gives you a superpower: **understanding**. When you can reason clearly about your own application code then you're in a good, future proof, place. No magic. -2. I'm not after performance for it's own sake. It's JavaScript man, not Rust. As long as performance is good, I prefer clean, readable, maintainable code. I don't want to need 10 coffees to understand what I wrote. -3. I'm not chasing DX above all. Oftentimes too much comfort means "magic" solutions, where we loose track of what's going on. This quickly becomes un-debuggable and impossible to reason about. I don't trade long term understanding for immediate comfort. +1. The focus is on having **clean mental models** for every part of the stack. + Which gives you a superpower: **understanding**. When you can reason clearly + about your own application code then you're in a good, future proof, place. + No magic. +2. I'm not after performance for it's own sake. It's JavaScript man, not Rust. + As long as performance is good, I prefer clean, readable, maintainable code. + I don't want to need 10 coffees to understand what I wrote. +3. I'm not chasing DX above all. Oftentimes too much comfort means "magic" + solutions, where we loose track of what's going on. This quickly becomes + un-debuggable and impossible to reason about. I don't trade long term + understanding for immediate comfort. ## Architecture @@ -16,10 +25,13 @@ The current pieces are (more to come): ### [Functorial](./packages/functorial/README.md) -A new `Proxy`-based reactivity system, that goes beyond Signals. More idiomatic. More granular. +A new `Proxy`-based reactivity system, that goes beyond Signals. More idiomatic. +More granular. -It's a structured way to declaratively interact with web API in a reactive manner +It's a structured way to declaratively interact with web API in a reactive +manner ### [Reflow](./packages/reflow/README.md) -A minimal frontend framework powered by template tags and providing Functorial mappings to all common web APIs. +A minimal frontend framework powered by template tags and providing Functorial +mappings to all common web APIs.