"The messaging system can become a bit convoluted, especially using the parent-child methodology"

[dharmaturtle]

The messaging system can become a bit convoluted, especially using the parent-child methodology I employed. I could see this quickly become difficult to use for a much large web application. In exchange, however, each part of the website could be built in near isolation.

I have very little experience with scaling MVU apps. However I've been reading up on how Elm does it, and they seem to eschew parent/child/componentized thinking. Since you know F#, Elm will be very readable to you.

Here's a video I found useful: https://www.youtube.com/watch?v=DoA4Txr4GUs

I'm currently trying to figure out how to scale my own Bolero app - though I'm not currently happy with it.

Just some thoughts - not really an issue. Feel free to close.

[kojo12228]

Thanks for the link, @dharmaturtle

I followed the Elmish parent-child model. Actually, it's not too dissimilar to what Richard described in the video. You can see it in even more detail in the Elmish book. One other decision I made was to make all my website pages use PageModels, as I didn't need any state to persist after leaving a page.

The aspect of Elm that would make Bolero/Fable/Elmish projects even simpler would be extensible records.

I'll keep this issue open and create a pull request later trying to incorporate some of the advise for the video.

[dharmaturtle]

Glad you found it informative. Also gonna direct you to, of all things, the comments on this youtube video:

Christer van der Meeren is a maintainer on the Elmish.WPF library.