The technology you use for your backend is entirely dependent on the use case you have. You could just stick with Python and write an API using Django or Flask or use another Lang and framework like C# and ASP.NET Core to build it.
If you need Server side rendering, nodejs would be your best bet. And like this your requirements will change.
If you're just doing it to learn something new. First learn how to build and connect the API in Python to a React app and then move to learn a new language/framework
Ultimately it's what you want out of your API that decides the technology you use.
Well everything has its pros and cons. But frankly if you do it right react with hooks is more helpful than you realize. When things start messy that's when you should start looking into the context API and then if it gets more complex you'll need to look into state Management libraries like Redux or MobX
An experienced software developer with a strong background in developing award-winning web and mobile applications for diverse clients with 6+ years of industry experience.
Not if you're using for it's designated purpose. If you end up making contexts for too many things then you've missed out on using something like Redux to reduce that problem. But using Contexts for the right problem is what makes it useful
An experienced software developer with a strong background in developing award-winning web and mobile applications for diverse clients with 6+ years of industry experience.
You have been lied to, there is absolutely nothing wrong with context API or creating contexts to handle different things, even react-redux uses it under the hood.
I never said there was anything wrong with it. I simply meant that there's a time and place to use the Context API and that you shouldn't use it for everything. There are times where you may need to shift to something bigger like redux. But you shouldn't if it's not required.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The technology you use for your backend is entirely dependent on the use case you have. You could just stick with Python and write an API using Django or Flask or use another Lang and framework like C# and ASP.NET Core to build it.
If you need Server side rendering, nodejs would be your best bet. And like this your requirements will change.
If you're just doing it to learn something new. First learn how to build and connect the API in Python to a React app and then move to learn a new language/framework
Ultimately it's what you want out of your API that decides the technology you use.
Ive been using Django and like how creating fields and accessing the data is really easy. React, with hooks, kinda adds clutter to the steps.
Well everything has its pros and cons. But frankly if you do it right react with hooks is more helpful than you realize. When things start messy that's when you should start looking into the context API and then if it gets more complex you'll need to look into state Management libraries like Redux or MobX
Things getting messy using context API depends entirely on the Developer.
Not if you're using for it's designated purpose. If you end up making contexts for too many things then you've missed out on using something like Redux to reduce that problem. But using Contexts for the right problem is what makes it useful
You have been lied to, there is absolutely nothing wrong with context API or creating contexts to handle different things, even react-redux uses it under the hood.
I never said there was anything wrong with it. I simply meant that there's a time and place to use the Context API and that you shouldn't use it for everything. There are times where you may need to shift to something bigger like redux. But you shouldn't if it's not required.