you picked the "wrong" framework as in you should have picked the other framework.
you wasted time debating yourself what to pick longer than necessary.
the first one is not as problematic as the second. let me explain.
it is reversible. so once you realized you made a wrong choice, you can simply stopped and switched. yes, the time spent previously is lost but is not a complete loss because a lot of the concepts can be carried over as both follow the MVC structure. Django calls it MTV but is different names for the same thing. any experience building a website with one framework also can be reused when you switched to another framework because the experience is more to do with the nature of website building than the specific framework itself.
you need to debate with your self but beyond a certain point any additional debating is a waste and this is a complete waste. none of the time spending extra debate / research is transferable to any django or ror frameworks. none of the time spending extra debate / research is transferable to the general experience of building websites.
so once again pick the lesser of two evils. Do enough research set out a criteria, then apply that criteria and choose. Dive in deeply into one framework. Set a timebox on when to re-evaluate your choice. I recommend evaluating after building 3 mini sized websites or 6 months of part time building at abt 10 hrs a week at least, whichever is longer. If you can build full time (i.e. abt 30-40 hrs a week), then shorten to 3 mini-sized websites or 2 months of full time whichever is longer.
@kimsia I appreciated your response. I think for now I'll go with Django. After 3-4 products. I'll see if I want to change the framework. Thanks for clearing my doubt. Also, if I'm going with Django. What should I do? do I first learn the full framework or just learn the API part and for the frontend, should I learn react.js?
Personally I thought be better for me if i learn how to do headless ie split into django backend and then react frontend.
I did kinda do that for that client project I told you from earlier.
Looking back I will say it’s a mistake.
In order to master react I needed time I don’t have.
Now my frontend is horribly outdated and I have no time to properly improve it
Ultimately my goal is same as you : build a product like a SaaS and run it as owner
If u need nice Ajax effects u can always try htmx which is good enough
Now I’m trying to slowly transition away from react to htmx.
I now agree with the philosophy of run less software by intercom. Google that article read it then hopefully you understand. I regret not knowing this earlier but like I said nothing is truly wasted. Just a matter of going shorter route or the longer route.
@kimsia In regards to react, you basically decided the time investment of both mastering Django and React together is too high so you wanted a simpler frontend? is that right?
There are only two mistakes you can make:
the first one is not as problematic as the second. let me explain.
it is reversible. so once you realized you made a wrong choice, you can simply stopped and switched. yes, the time spent previously is lost but is not a complete loss because a lot of the concepts can be carried over as both follow the MVC structure. Django calls it MTV but is different names for the same thing. any experience building a website with one framework also can be reused when you switched to another framework because the experience is more to do with the nature of website building than the specific framework itself.
you need to debate with your self but beyond a certain point any additional debating is a waste and this is a complete waste. none of the time spending extra debate / research is transferable to any django or ror frameworks. none of the time spending extra debate / research is transferable to the general experience of building websites.
so once again pick the lesser of two evils. Do enough research set out a criteria, then apply that criteria and choose. Dive in deeply into one framework. Set a timebox on when to re-evaluate your choice. I recommend evaluating after building 3 mini sized websites or 6 months of part time building at abt 10 hrs a week at least, whichever is longer. If you can build full time (i.e. abt 30-40 hrs a week), then shorten to 3 mini-sized websites or 2 months of full time whichever is longer.
That should cover most edge cases i can think of.
@kimsia I appreciated your response. I think for now I'll go with Django. After 3-4 products. I'll see if I want to change the framework. Thanks for clearing my doubt. Also, if I'm going with Django. What should I do? do I first learn the full framework or just learn the API part and for the frontend, should I learn react.js?
Welcome 🙏
There is no “should”
Personally I thought be better for me if i learn how to do headless ie split into django backend and then react frontend.
I did kinda do that for that client project I told you from earlier.
Looking back I will say it’s a mistake.
In order to master react I needed time I don’t have.
Now my frontend is horribly outdated and I have no time to properly improve it
Ultimately my goal is same as you : build a product like a SaaS and run it as owner
If u need nice Ajax effects u can always try htmx which is good enough
Now I’m trying to slowly transition away from react to htmx.
I now agree with the philosophy of run less software by intercom. Google that article read it then hopefully you understand. I regret not knowing this earlier but like I said nothing is truly wasted. Just a matter of going shorter route or the longer route.
@kimsia In regards to react, you basically decided the time investment of both mastering Django and React together is too high so you wanted a simpler frontend? is that right?
If I can go back in time I will say to my previous self
“success is a multi variate function”
If under different circumstances eg i have enough free time under no work pressures will find django and react still too much?
Will a different person with my exact circumstances come to same conclusions?
I have to be intellectually honest
Not necessarily
Out of the same honesty value was it too much for me?
Yes and for the foreseeable future as well
For what I want to accomplish do I absolutely need react? No
Hence my conclusion is highly personal to my unique circumstances and my own innate capacity
Different people may reach different conclusions.
I make no sweeping statements about django or react in and of itself.
My comment only covers the interaction of my experience with those domains plus my circumstances
I can tell you I spent a lot of money trying to be good at react close to 1500 dollars over a few years
I really tried