Discovering and mastering bacon.js&#x2F;FRP completely changed the way I think about programming. It hugely increased the quality and stability of my code in ways that continue to surprise and amaze me. I cannot recommend it enough, but this article definitely has me curious about ClojureScript.<p>In the meantime, the biggest issue I&#x27;ve had with bacon is figuring out what are the best practices in organizing the code. One does end up with a lot of streams or variations&#x2F;combinations on streams used for different purposes. Eventually it does become hard to follow, as the author mentions, though because all state is self-contained you can change any one part with a high degree of confidence that it won&#x27;t break other features.<p>Still there must be some ideas out there that don&#x27;t involve incorporating a full blown framework&#x2F;SPA architecture. The author of bacon has a blog post on the subject but it seemed to me that there could be better ways still. Anyone have any suggestions?