3 ms·
I can see why you went full GUI to begin with now. The example component code reminds me a lot of mobx-state-tree (you have no idea how much cog. diss. I get r
by mst 2y ago
I can see why you went full GUI to begin with now.
The example component code reminds me a lot of mobx-state-tree (you have no idea how much cog. diss. I get reading the docs for that thing given they acronym the name everywhere ;) though I find myself much preferring the API shape of mobx-keystone at this point.
(I've been experimenting a lot with reactive graphs of late though while it seemed an obvious thing to try at some point I haven't attempted to wire it up to systems automation yet; shall have to do my usual cover-to-cover documentation read on your site and then hopefully I'll be in touch with a baseline to actually chat about that part ;)
- holoway 2y agoI mean, we didn't start there - we wound up there :) But yeah, you're not wrong that it's got a lot of inspiration from things like mobx and rxjs.
- mst 2y agoYeah, I guess I meant "for release 0.999_001" [1] or something rather than a strict interpretation of "to begin with." > But yeah, you're not wrong that it's got a lot of inspiration from things like mobx and rxjs. Please figure out how to deploy a subset of the reactive graph into a k8s operator. It'll be a really cool feature and also it'll probably save me a bunch of time when I want one of those if I can crib from your work :D I ... bah. I am really looking forwards to getting into another of our involved coversations about this stuff but I'm too tired today and besides I definitely do need to mainline your docs first. I'll probably see you on twitter first with the assumption you'll end up chasing me onto Discord sooner or later ;) [1] please interpret that in terms of how you remember me (ab)using version numbers ;)