No, but the pendulum might be swinging back towards more server driven apps using WebSockets or other techniques to reload page elements vs. front end SPA. The

No, but the pendulum might be swinging back towards more server driven apps using WebSockets or other techniques to reload page elements vs. front end SPA. The front-end still needs to be developed but if its served from back end code then I can see a lot lighter front-end work. From my naive understanding there are a lot of JS frameworks/libraries that deal with validation of user input, maintaining state of data+DOM and tests around ensuring those things are taken care of, entirely in front-end code. All of those things can be done from the back end and the dynamic refresh of data/page is taken care of with less JS on front-end. From a back end perspective, the back end has to check inputs coming into controllers and have tests around what has to happen before doing DB operations so a lot of the work in front end to do similar seems redundant. All that being said, there is still a lot of work that goes into building a front end for an application. Even if it is back end code generating the HTML/CSS for page fragments, they still have to work in a cohesive way on the front-end. If you can be conversant and learn similar things (maintaining state, validation, tests) in whatever back end language is used then you should be fine.