One option is to eschew front-end and do to work for a large company where roles are so defined that there are jobs that truly are back-end. Pretty much anywher

One option is to eschew front-end and do to work for a large company where roles are so defined that there are jobs that truly are back-end. Pretty much anywhere else you go, even if the role is "back-end", there is a chance you'll have to touch front-end at some point. I wouldn't suggest that, especially since you started off with JQuery. If you don't mind probably rewriting everything and don't have models that are that complicated, you could take a look at Electrode. I've not used it, but the goal of their project was to hide the complexity of JS front-end: http://www.electrode.io/ http://www.electrode.io/ Angular or Ember are opinionated frameworks that might be good to use if you can give up JQuery and just embrace something new. The following has an answer which suggests Meteor also- it's cool, but is a more specialized use case that might not be appropriate for everyone. Also note that the opinion on Ember being better than Angular is pretty biased- it really comes down to what makes sense and is comfortable: https://www.quora.com/React-Angular-Meteor-Ember-Vue-etc-In-what-specific-cases-would-you-choose-to-use-one-framework-or-the-other https://www.quora.com/React-Angular-Meteor-Ember-Vue-etc-In-... However, if it just doesn't matter and you are just doing it to try to stay current, I'd argue to not jump to a new framework unless it makes things easier for you and your team. There are benefits to using what is popular in the development community, more specifically in the pools of development talent you have available to your company. But, in the end, what matters is your productivity. Are you getting more done now than you used to? If not- you shouldn't be doing it.