-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consideration: discussion of modules, scope and modularity #6
Comments
One pattern I've had success with is a "wide diamond" of modules. I have I wrote an article on scope, which I've been meaning to do anyway. It's more syntactic than architectural, but hopefully it's helpful in some way. |
Nice. TY! |
This may just be a me-specific problem, but I'm missing a decent conceptual grounding about how modules impact scope. Specifically, I'm grinding at the moment about how to achieve decent modularity yet still share central nervous system things like signals and addresses.
Current example apps abound, but they are all fitted to very small uses cases and demonstrate "statement use" rather than how a real-world app would hang together. Even ToDoMVC fails that test.
Yes, I'm reading EC's architecture notes, but they are rather "by an expert, for experts"; I'm neither.
Alas.
The text was updated successfully, but these errors were encountered: