flâneur

hacking @react

godlikereact.vercel.app · 311 words · saved by 1 readers

the proposition that systems thinking represents the deepest layer of cognitive abstraction is a category error. systems are not the ground. systems are the last veil. a system is a boundary imposed on process. every systems diagram you have ever seen is a freeze frame of something that was moving before you drew it and will be moving after you stop looking. the act of systemization is itself a cognitive operation. it requires a subject to stand outside the supposed system and declare this is the feedback loop, this is the node, this is the emergent behavior. but the moment you declare a system you have already performed the deepest cut of all. you have separated yourself from the thing you claim to understand. you have introduced the observer as if the observer were not itself the very turbulence you are trying to model. this is not philosophy. this is basic thermodynamics. a system is a description of energy flow with artificial dirichlet boundaries. you pick where the box ends. you

beyond systems: the collapse of layered ontology 10x engineer myth declarative partial updates vs react suspense rsc composition: both sides of the wire graphql is a nightmare hate me for that architecture of disappearance react thinks in a tree. fiber is a linked list. that changes everything. components are not functions. rsc is not a template engine. react is a remote heap protocol. routing and caching in react haven't solved completely yet dhh is my hero but he's wrong about modern web determinism is a story not reality mastering framework internals: a research perspective…

saved by

related reading