Best of luck to you! If your primary goal is to tinker and learn new things, then of course you should use whatever you're curious about. But if your primary objective is to build a working app and get it to a point where you can test out if the market is biting, then I'd suggest using a stack you're already familiar with. That will help you iterate as quickly as possible, and you'll be more focussed on building features rather than debugging. If your technology choice limits you in some way down the line, I'd proffer that it probably means your app is already successful enough for that to be a good problem to have. I'd wager the truth of the matter is that any well-established technology will have its fair share of good and bad in the end though.
This is a very good point. TBH, I think having an app big enough to be a problem is akin to having a hit record in the 80s - possible, but unlikely... . Sigh.
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.
Best of luck to you! If your primary goal is to tinker and learn new things, then of course you should use whatever you're curious about. But if your primary objective is to build a working app and get it to a point where you can test out if the market is biting, then I'd suggest using a stack you're already familiar with. That will help you iterate as quickly as possible, and you'll be more focussed on building features rather than debugging. If your technology choice limits you in some way down the line, I'd proffer that it probably means your app is already successful enough for that to be a good problem to have. I'd wager the truth of the matter is that any well-established technology will have its fair share of good and bad in the end though.
This is a very good point. TBH, I think having an app big enough to be a problem is akin to having a hit record in the 80s - possible, but unlikely... . Sigh.