Quote:
Originally Posted by Beasting
What is the reason behind that? To my knowledge from a few years ago, front end was more or less for web designers, whereas the "developers/engineers" handled the back end. I could be wrong but that was my impression.
Mostly it's due to increases in network efficiency and javascript performance. It's not so much that javascript has replaced tradtional (server-based) web apps as it is that javascript apps have replaced programs you used to run on your desktop. So a lot of things that used to not really be web-dev jobs sort of became web-dev jobs.
Networks becoming faster or more available in general means that it's more feasible to have all the code running on the FE and making API calls to a backend, where the older model was "the FE makes one call to the backend, which does all the work and returns a buttload of stuff"
Most of the web stuff I've worked on recently has pretty simple backend APIs with more complex logic in the front end. Single-page apps double down on this philosophy.
Quote:
Originally Posted by Beasting
That sounds logical enough. The educational path I've begun is geared toward web development. Do you think that's a good starting point, or in your view is there a better (more strategic) path to go down when starting from scratch?
I have known a lot of web devs with big gaps in their programming knowledge, because they were not called on to do certain things. This is even more true for javascript-centric developers because literally their whole life is spent in the browser.
It's difficult for me to tell whether those gaps are "big problems" or not, people tend to over-estimate the importance of what they know how to do.