I just fell in here from the HN thread. I just discovered this field and it's so surprisingly close to the coding methodology I have been stumbling towards for some time and I'm delighted. I got really into using concatenative programming styles in TS (enabled via ramda and lodash/fp) and this is such an obvious next step - I'm also (embarrassingly) just coming to RxJS now, but skilling up very quickly as this fits how I was already thinking.
Is anyone working on using Connective+RxJS to do Behaviour Programming?
.control mechanism on node() and expr() returns
expr() is just a special-case node() that only has one pinout, is that right? node() is a generalization of expr()?
@moltar so as I mentioned (and you suggested), I have started working on a pure-DOM rendering library that nicely works with RxJS and CONNECTIVE. I considered utilizing LitElements for this project, however generally there are some bits and pieces of WebComponentsAPI that are not universally standardized (or at least it feels as such) so I basically opted for creating a library that can later be minimally modified to utilize the WebComponents API and something like LitElements for its component-based rendering (still keeping my hopes up for poor pure Polymer).
The project is basically a custom TSX/JSX renderer that produces raw DOM Elements (so no VDOM), supports minimal element lifecycle (binding, clearing up), and hence can also render Observables or Pins seamlessly (this is the step that the project currently is at). Furthermore, it should support functional components quite easily and seamlessly, from pure templates to complex components (I suspect this should be quite easy as we can just create a composition() and attach it to the rendered element's lifecycle). The overall goals of the project are:
- being quite straight-forward (as in RxJS/CONNECTIVE straight-forward) explicit TSX/JSX coding
- having no magical layers (no VDOM, no framework-specific compilation, etc), just based on Typescript's default TSX support (so also minimal setup/development pipeline)
- being explicit, which is already what RxJS/CONNECTIVE state management would require, but also on all other fronts
- being surgical, which (mostly) naturally results from being reactive and explicit, but also means in theory the end result should fair much better performance-wise than most other JS frameworks out there.
All of this means the envisioned end-result is something like this gist.
The project is in super early stage so everything can and will constantly change. You can run the code by doing npm start and then opening samples/index.html, which is basically running samples/index.tsx.
I do not think this will be a heavy-lifting project, but still I definitely could use a lot of help on this, specifically with regards to performance optimization / example use-cases / etc. So if you are interested, do not hesitate to join in! 😎
EDIT: I mentioned Roman since he has brought up the idea before but this post is towards everyone.