Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 2
    This seems like a classic example of what happens when you have a hammer and everything looks like a nail. Commented Jun 28, 2018 at 20:56
  • @RobertHarvey If this is not an appropriate use of reactive programming, I seriously question whether one exists. Wanting to go from Stream Product to Stream HTML seems like a pretty textbook example. Commented Jun 28, 2018 at 20:58
  • More like stream.product to stream.invoice. I don't know enough about the reactive libraries like react.js to offer an opinion about UI elements, other than these libraries are strongly related to data binding and are a replacement for events. I don't know anything that serves as a black box for transforming data into html pages directly, except perhaps for XSLT. Have you written anything practical using streams yet? Commented Jun 28, 2018 at 22:14
  • See also baconjs.github.io Commented Jun 28, 2018 at 22:17
  • @RobertHarvey My question isn't about how to generate HTML, nor is it about react.js (which doesn't seem to have much to do with reactive programming), or even JavaScript specifically. I have used bacon.js, RxJs, and xstream, and in my opinion none of them offer a good solution to this problem. Yes, I've written practical production code with streams and it's wonderful when it works; when it doesn't, as in this case, it's hair-pullingly frustrating. Commented Jun 29, 2018 at 0:37