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.

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.

Promised - async

Observables - streams

Signals - reactivity

“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.”

And it really doesn’t matter why some countries got poorer, this is the fact right now so my point still stands.

Having all countries open the borders to anyone (ignoring security risks for the sake of the argument) would mean all poor people would emigrate to rich countries and strain the economy, while their home country would collapse from lack of workforce.

You used to have a couple of days to close a breach, now it 2 hours.

When working with react I hated how components became hundreds of line of code with tons of intertwined hooks.

Heavily inspired by Angular’s mental model, I sought to bring 3 things into react -

- separate business logic from the rendering layer

- true reactive state using signals

- an easy but robust dependency injection system to share state, or replace implementations

Beyond that, I added some utils like async signal, forms management, and testing tools

I’d love to hear your opinion!

Comments URL: https://news.ycombinator.com/item?id=48184318

Points: 1

# Comments: 0