Go with what you know can get the job done. It's fun to use new tech, but Java isn't going anywhere and it's very stable and performant at this point.
Your concerns should be the following:
1 - will this stack get the job done, and at a reasonable velocity
2 - will you lose time because you need to ramp up on a technology you're not familiar with
3 - how maintainable will this be for developers who come after you?
Spend time figuring out what you'll need to accomplish for this project, and then decide which framework will work best for it.
If you're still not sure what to go with, it can be really worthwhile to do a quick proof of concept that covers the areas you feel most uncertain about. I did this before choosing Elixir for a recent project, and it helped me feel a lot more confident in that choice.
Outside of your freelancing, I'd encourage you to spend time using new tools are frameworks. That way, you'll know the strengths and weaknesses of each before you need to pick one for a project.
Comments
Go with what you know can get the job done. It's fun to use new tech, but Java isn't going anywhere and it's very stable and performant at this point.
Your concerns should be the following:
1 - will this stack get the job done, and at a reasonable velocity
2 - will you lose time because you need to ramp up on a technology you're not familiar with
3 - how maintainable will this be for developers who come after you?
Spend time figuring out what you'll need to accomplish for this project, and then decide which framework will work best for it.
If you're still not sure what to go with, it can be really worthwhile to do a quick proof of concept that covers the areas you feel most uncertain about. I did this before choosing Elixir for a recent project, and it helped me feel a lot more confident in that choice.
Outside of your freelancing, I'd encourage you to spend time using new tools are frameworks. That way, you'll know the strengths and weaknesses of each before you need to pick one for a project.
This