4 ms·
The deep idea we're really aiming for is proper separation of concerns. Hyperfiddle isolates your web clients from network I/O, so your components can stay decl
by dustingetz 8y ago
The deep idea we're really aiming for is proper separation of concerns. Hyperfiddle isolates your web clients from network I/O, so your components can stay declarative, data-driven and pure, and thus compose/nest arbitrarily deep and in recursive ways. If we accomplish this, it should compose a lot better than the ball of mud imperative UIs and APIs that make up today-era applications.
- madrox 8y agoAgain, I think the benefits of what you're describing only matter in larger apps. Separation of concerns come up in large projects where people of different disciplines get together...or you want to be disciplined about abstractions and re-use. However, when you get to that point, you're going to want specialized tools to manage each component. Code is code and it still needs to get audited. To address this, I recommend thinking about decoupling the technology from the workflow.
- dustingetz 8y agoIt already is