RxJS vite plugin that operates in much the same way as react devtools and vite plugin, because I love rxjs but I cannot recommend it without that same calibur of tooling. Turns out you can take a lot of ideas from the react vite plugin and do a bunch of similar things.
Trying to parse, model the HMR process, and storing the data as flat as possible and doing it from relation design first, has been a pleasant process.
Im hoping it works for react devs easily, and then I guess I'll try to learn angular to see if that would not be helpful for them too.
I mostly want to help my old coworkers maintaining my old crazy code with a visual helper.
yup, all these folks claiming AI is the bees knees are delegating their thinking to a roulette that may or may not give proper answers.
the world will become more and more like the movie idiocracy
I got really good at rxjs and saw a way to make a custom jsx transform where every element is an Observable of string. I've been using it to make my site/blog and just got done writing a mini self contained jira board to iron out the interactivity aspects.
Since it's strings, I just render to file for backend static site generation, then frontend I use diffDom library to do efficient (enough) updates from html string without destroying dom state.
It works really well, but I also don't allow inline event listeners (they make everything much harder), so I've been learning how to leverage event delegation. All in all a pretty fun side project.
You've sent me down a really interesting rabbit hole as someone who is trying to move away from just writing and understanding how React works. Can you explain a little more why this felt worth pursuing? I'm interested in what sorts of advantages this could have.
1. Async and conditional effects without hopping component boundaries with switchMap
2. React.Context ritual vs oneliner `pipe(shareReplay)`
- this is easily the most useful thing, in lines of code alone
3. React is used shallowly for jsx and html, and rxjs is used for events and state and quite literally everything not writing to the dom.
4. Lazy by default, no need for suspense bc it's inherit property of observables.
5. Merge and combineLatest give you algebraic tools for constructing your logic instead of stringing components down a subtree
6. Scan but that's just inline redux reducer but I use it all the time
7. Observables are on standards track for HTMLElements in browser.
- element.when('click').map/filter/takeUntil etc.
I view react as promises--. You have to do wildly hacky things using custom API ideas that change between majors, can only use sync functions, yet all your logic is async. It's like the function coloring problem on steroids.
The maiden voyage of my blog will be soon, it's first big write up will be the test page for this jsx transform, then I'm gonna be writing a field guide for how to translate between react and rxjs.
