Thanks for the detailed comment! I always heard that bees pollinate the vast majority of plants, so in the parent comment, I assumed incorrectly that the meaning was for bees in general being non native.
Jest mocks allow developers to write bad code. Instead of separating concerns with DI, jest mocks overwrite the importing mechanism without any type safety. Also, if you wish to migrate to native node test runner, the mocks lock you into jest.
Use proper mocks with ts mockito and it will force you to write better code.
Israel has clearly defined borders. If youre are talking about the West Bank there’s area a, b and c which are controlled by Israel, both, and PA respectively. I’d call that borders.
When all you need is a synchronous operations, yes. When it involves async, batching, buffering, and user input, it becomes much more complicated, and every step needs to be setup manually.
Agreed, the OP said that the r in rxjs stands for reactivity, so my point was the the names have little bearing on the actual design patterns achieved with the libs
Maybe push pull wasn’t the best metaphor, but the point is that everything can be reactive, it only depends on how much boilerplate you need to write to achieve the desired result.
Since react doesn’t have a true reactive model, you need to subscribe to changes manually (use effect) to create computations, while in signals it’s a primitive (computed).
I actually created a lib that operates signals over reacts state management (https://roypeled.github.io/react-logic/), so I removed the boilerplate to create a true reactive system.
If you want, you can create reactive system just from JS primitives, using callbacks. But that doesn’t make JS reactive by nature.
I partially agree, there is an overlap between signals and rxjs, however the core business is different- observables are about data manipulation, while signals are about efficient state management.
Regarding angular I agree, rxjs was a bad choice for data management, and before signals arrived I abandoned rxjs in favor of mobx in my angular projects. However you could roll your own http client, we used axios, and using DI it’s a drop in replacement.
Don’t like to cast stones, but this feels like Claude trying whatever it can to make things work, without fixing the underlying process and problem.
“It looks like the user wants to run curl on windows machine, I need to bootstrap Linux under docker, and channel bash commands into shell inside docker, so the user would be able to run curl natively.”