No, the decision on the front-end or back-end is not about dating, but perhaps “updating”, or building something new. You of course know this refers to technology. More specifically application code. Code is developed in two separate but integrated areas. One is the “front-end” which is the visible part of the User or Customer Experience (UI/UX or CX). The second is the “back-end” which is not visible and is relegated to managing data. OK, the question of which is more important is admittedly rhetorical. One has no meaning without the other. The real question is how you decide what coding language you use for each. That question does deserve some examination.
Without listing what may be meaningless names of front-end and back-end coding languages, the choice depends on the specific needs of the application being developed. Application speed, resource consumption (and related costs), and availability of skilled people are typical considerations that affect your choice. Furthermore, if you are not doing all the work yourself your application development partner will work with you to decide on the best approach for the front end and back end.
Customers more often expect us to do due diligence to decide what is best for them, and to explain why. In fewer cases, where it may involve updating an existing application, they share with us their technology stack which defines what must be used for the front-end and back-end.
DesignRush, whom TIMIT has partnered with, has a helpful article on this subject regarding just one of the back-end example coding languages (node.js) you can read it here: https://www.designrush.com/agency/software-development/trends/why-use-node-js.
If you would like to discuss your specific needs, we would love to discuss them with you. Schedule a 30-minute call here: https://calendly.com/tim_montgomery/custom_app_discussion.