summaryrefslogtreecommitdiff
path: root/Biz/Devalloc/Node.hs
AgeCommit message (Collapse)Author
2020-12-06Remove Miso from DevallocBen Sima
I decided to finish the Devalloc frontend by just removing it. This way I can have everything in one file, the code is much simpler, and I can scale up as needed. Anyway, this works fine with Turbolinks and that's pretty cool, so you get the same basic feel as with any other SPA.
2020-12-06Finish Devalloc miso app prototypeBen Sima
After hours of trying to get a page abstraction working in a Miso app (both Devalloc and Hero) I had a revelation: Miso is an SPA - *single* page application - framework, and so trying to put multiple pages into it is fundamentally at odds with the rest of the architecture. Of course this is also a problem with Elm's pattern of nesting models in order to create a page abstraction. They can pull it off because they don't also try to do isomorphic rendering. In hindsight this should be obvious... if I actually do want some kind of page-like abstraction or separation, then I need a much more complex server that can embed different Miso apps based on some logic. But this is more like multi-tenancy, or something. Also I'm starting to think that I don't want Devalloc to be an SPA anyway, so I'll try an experimental branch where I rip it out and just use Servant, Lucid, and Turbolinks.