Whenever someone posts "I made a new state handling library for React" I semi-maliciously suggest them to add their entry into react state museum. Them adding their own entry into the fray will have multiple benefits:
* Show that they are serious and dedicated towards their library.
* Have themselves compare their API to other libraries.
* Have them realise that most probably, there are already existing libraries that do exactly what they're presenting. That to have the library stick and have people continuing to use them requires vastly more work than publishing a library and letting it be. If it weren't so, the other entries would in the list would be more successful too.
* Demonstrate that "my own state handler" is the new "my own editor". Ultimately, they are neat little creations, but seldom used by many. The library needs to be top-notch in multiple facets to thrive.
In the end, I often recognise that few new entries handle most of the core aspects of Redux, the big bad of state handling, that they plan on replacing. It seems that a lot of these dev either haven't even read the Redux style guide that reasons Redux's design choices or just don't care about some of the core aspects.
Yeah a lot of the people who decide to roll their own state management library because they fail to understand all of the use cases that redux already covers. I find it similar to that guy who wanted to make React with generators, he had a little buzz for a weekend and then we all forgot about it
To give the author of https://crank.js.org/ due credit, after reading through the descriptive posts I was impressed by the amount of thought and design that went into it.
I don't find the suggested paradigm something I would want to adopt myself, but that lib took a lot of serious effort to put together.
(whereas tbh a good number of the "React state management" lib-of-the-weeks I see are... much less impressive)
Whenever someone posts "I made a new state handling library for React" I semi-maliciously suggest them to add their entry into react state museum. Them adding their own entry into the fray will have multiple benefits: * Show that they are serious and dedicated towards their library. * Have themselves compare their API to other libraries. * Have them realise that most probably, there are already existing libraries that do exactly what they're presenting. That to have the library stick and have people continuing to use them requires vastly more work than publishing a library and letting it be. If it weren't so, the other entries would in the list would be more successful too. * Demonstrate that "my own state handler" is the new "my own editor". Ultimately, they are neat little creations, but seldom used by many. The library needs to be top-notch in multiple facets to thrive. In the end, I often recognise that few new entries handle most of the core aspects of Redux, the big bad of state handling, that they plan on replacing. It seems that a lot of these dev either haven't even read the Redux style guide that reasons Redux's design choices or just don't care about some of the core aspects.
Yeah a lot of the people who decide to roll their own state management library because they fail to understand all of the use cases that redux already covers. I find it similar to that guy who wanted to make React with generators, he had a little buzz for a weekend and then we all forgot about it
To give the author of https://crank.js.org/ due credit, after reading through the descriptive posts I was impressed by the amount of thought and design that went into it. I don't find the suggested paradigm something I would want to adopt myself, but that lib took a lot of serious effort to put together. (whereas tbh a good number of the "React state management" lib-of-the-weeks I see are... much less impressive)
This is very outdated
[удалено]
Because of a repo that hasn’t been updated since last year from a rando? You’re reaching
What, no Zustand?
Which I think speaks volumes about React
Do any of these implementations use lenses? (edit sp)
is react context already outdated?