blocks|key|818201|text|我个人更倾向于Redux。但是，如果你是一个初学者，试图学习Redux，你可能会有一些困难，直到你理解它。一旦你得到它，你也会喜欢它。与其构建您自己的自定义钩子，不如像使用Redux一样使用Redux+/您对某些东西很感兴趣，您需要支持社区，您还可以使用一些中间件库(如redux-thunk等)分派异步调用。您也可以在表单中使用Redux。我想如果你结束建立你的定制钩子，你可能会浪费时间，照顾所有这些。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|818202|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I am personally more inclined towards Redux. But if you are a beginner trying to learn Redux you might have some hard time until you understand it. Once you get it you will also like it. Rather than building your own custom hook, It's better to use Redux as if anything goes wrong/you are struck with something, you have community to support and You can also dispatch async calls using some middleware libs like redux-thunk, etc. You can use Redux with forms as well. I guess if you end building your custom hooks you might end up wasting time, taking care of all these.

blocks|key|818223|text|当然，使用Redux更好，因为使用Redux处理大型应用程序更容易。它只有一个存储，基本上是一个javascript对象。您可以将存储分成多个部分，每个部分将针对应用程序的特定部分。所有这些部分都将使用redux提供的combineReducers函数连接在一起。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|818224|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Of course, it is better to go ahead with Redux, because it is easier to handle large applications with Redux. It has only a single store, which is basically a javascript object. You can divide the store into many pieces, each piece will be for a particular part of the application. All these pieces will be joined together using the combineReducers function provided by redux.

blocks|key|1629987|text|has是一个状态管理库，随着React钩子的发布和对React上下文的大规模改进，这种状态管理方法已经大大简化。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1629988|我认为，在99%25的情况下，我们不需要redux，并且为项目增加了一层复杂性。对于大规模应用程序来说，redux可能是更好的选择。但是，如果您选择React进行状态管理，则需要有关一些概念的良好信息，这些概念如下：|1629989|本地状态与全局状态(一些组件需要本地状态，并且将它们的所有状态都置于全局状态会导致许多问题)。|ordered-list-item|1629990|react上下文和支柱钻削问题以及如何有效地使用React上下文|offset|length|1629991|反应钩，特别是useReducer和useContext|1629992|不变状态|1629993|entityMap|0|LINK|mutability|MUTABLE|url|https://kentcdodds.com/blog/prop-drilling^0|0|0|0|9|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|Z|8|@]|9|@$I|10|J|11|1|12]]|A|$]]|$1|K|3|L|5|F|7|13|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|14|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

React is a state management library and with the release of React hooks and massive improvements to React context this method of state management has been drastically simplified. 

I think in 99% of the situations we do not need redux and add one layer of complexity to project. 
For big scale app maybe redux is better choice. but if you choose React for state management you need good information about some concepts and this concepts is:

<ol>
<li>Local state vs global state(some component needs local state and putting all of their state in global state leads to a lot of problems) </li>
<li>react context and <a href="https://kentcdodds.com/blog/prop-drilling" rel="nofollow noreferrer">prop drilling</a> problem and How to use React Context effectively </li>
<li>react hooks especially useReducer and useContext</li>
<li>immutable state</li>
</ol>

blocks|key|2261942|text|你总是需要问自己一个问题:我需要额外的库吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2261943|Redux的受欢迎程度正在下降，这是由于对React本机状态管理的改进。这是有原因的！|2261944|如果你想为一家不新鲜的公司工作，你就有机会使用redux。我很幸运地说服我的团队使用我们自己的状态管理库构建，只使用React.useState。|2261945|如果您的应用程序状态逻辑非常简单，这意味着:状态大部分是本地的，共享状态大多在父-子关系之间，不同状态之间不严重依赖，那么我建议只使用React和useReducer+(如果您喜欢使用减缩器)。|2261946|一旦应用程序状态变得复杂，就需要有一些额外的全局状态管理工具。|2261947|关于React.useState，您需要知道的最重要的事情是，返回的setState函数是您与该组件状态的连接。让我们假设我们可以将该函数从组件中取出并在其他地方使用。通过这种方式，您可以使用一个函数从组件外部更新状态。|2261948|export+let+exportedStateSetter;

const+Component+=+()+=>+{
++const+[state,+setState]+=+useState();

++useEffect(()+=>+{
++++exportedStateSetter+=+setState;
++++return+()+=>+exportedStateSetter+=+undefined;
++});

++return+<div>{state}</div>
};|code-block|syntax|javascript|2261949|在上面的示例中，您现在可以导入exportedStateSetter并在其他地方使用它来更新该组件的状态。|2261950|这不是一个最好的例子，这是一个简单的可视化。|2261951|当您对此进行批判性的思考时，您就会意识到，现在您知道如何从组件外部设置组件状态，并知道如何在全局上设置状态。|2261952|我强烈建议使用这种方法来构建您自己的全局状态库，或者使用我根据我解释的内容创建的一些状态库：|2261953|npm+install+--save+react-global-state-hook++//+simple
npm+install+--save+rx-global++++++++++++++++//+complex|2261954|结束它:如果不是作业要求的话，不要使用Redux。您可以始终使用Redux约定，方法是将状态分离到存储区，用还原器更新状态，以及与状态交互的操作。为此，您可以使用本机响应状态管理，如果使用得当，不仅可以使用React.useState。React为您提供了您所需的一切，以及您所需的一切。|2261955|随着时间的推移，我对自己的库拥有了最好的开发经验。它迫使您理解一般的状态管理和正在使用的框架。|2261956|我对这两个图书馆的任何反馈意见都是开放的，如果你有任何关于国家的问题，请继续发帖。|2261957|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1A|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1B|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1C|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1D|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|1E|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|1F|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1G|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1H|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1I|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|N|7|1J|8|@]|9|@]|A|$O|P]]|$1|10|3|11|5|6|7|1K|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|1L|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|1M|8|@]|9|@]|A|$]]|$1|16|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]]|17|$]]

You would always need to ask yourself the question: Do i need an additional library?
Redux is on its decline in popularity, due to improvements on Reacts native state management. There is a reason for that!
If you want to work for a company thats not brand new, there is a chance you have to use redux. I was fortunate enough to convince my team to use our own state management library build only with React.useState under the hood.
If your application state logic is quite simple, meaning: states are mostly local, shared state are mostly between parent-child relationship and different states are not heavily depending on each other, then I recommend only using React useState and useReducer (in case you like to use reducers).
Once your application state is getting complicated, you need to have some sort extra stuff of global state management.
The most important thing you need to know about React.useState is, that the returned setState function is your connection to that components state. Lets assume we can take that function out of the component and use it somewhere else. This way you have a function to update your state from outside of your component.
<pre><code>export let exportedStateSetter;

const Component = () =&gt; {
 const [state, setState] = useState();

 useEffect(() =&gt; {
 exportedStateSetter = setState;
 return () =&gt; exportedStateSetter = undefined;
 });

 return &lt;div&gt;{state}&lt;/div&gt;
};
</code></pre>
In the example above, you can now import the exportedStateSetter and use it somewhere else to update the state of this Component.
!This is not a best pracitce example, this is a simple visualization.
When you think very critically about this, you will realize that now you know how to set a components state from outside of a component, you know how to set states globally.
I stringly recommend using this approach to either build your own global state library or use some that i have created based on what i explained:
<pre><code>npm install --save react-global-state-hook // simple
npm install --save rx-global // complex
</code></pre>
To wrap it up: Dont use Redux, if not required by a job. You can always use Redux conventions, by seperating state into stores, update state with a reducer and actions that interact with the state. For that you can use native React state management, if not only React.useState when used properly. React provides you with everything you need and everything you need to build yourself.
I had the best developer experiences with my own libraries that evolved over time. It forces you to understand state management in general and the framework you are using.
Im open for any feedback on the 2 libraries and if you have any questions regarding state, please feel free to keep posting.

Which technique is better for state management in react app?
Actually I want to create a big app where I've to manage my state which technique is optimal for state management context, Redux or react custom hook?

State Management in React

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

在react应用程序中，哪种技术更适合状态管理？实际上，我想要创建一个大型应用程序，在其中我必须管理我的状态--哪种技术是状态管理上下文、Redux或react自定义钩子的最佳选择？

问反应状态管理
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问反应状态管理EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问反应状态管理
EN