3
before marking as duplicate of the following question Difference between client-side and server-side.
Let’s look at some facts.
The previous question is from 2013 or 4 years ago, long before the rise of javascript frameworks "reactive".
- Angular JS = first appearance 2010
- Express.js = first appearance 2010
- Elm = first appearance = 2012
- React = first appearance = 2013
- Ionic = first appearance = 2013
- Angular = first appearance 2014
- Vue.js = first appearance 2014
What we are talking about only web frameworks, nowadays we know that javascript is no longer land without law, the language has evolved and today runs both in the server-side as in the client-side.
So it may seem a beast doubt, but today for example the angular consists of 3 main files in its "core".
- HTML
- Typescript
- SASS / CSS
we know that the angular consists of several categories of files responsible for some part of the application.
- Component
- Service
- Class
- Directive
- Guard
- Interface
- Pipe
- Module
These are some files that can be part of an angular project.
So today...
- a front-end developer must know how to handle the entire web framework ecosystem ?
- he is responsible for connecting the back-end with the front-end (using services for example) ?
- it is responsible for leaving the screens functional and dynamic ?
- or he is simply responsible for making only the visual (ux) ?
I’m still not sure if the question really deserves to be closed definitively, but I closed it preventively because this kind of question tends to attract bad answers, including because if you move depending on the day you’re reading the answer, it’s not good at all. In the present form it is not good and part of wrong premises, ambiguous, and I do not know if it is even in the scope and I do not know if I can answer this because there is probably no universal answer. I await other opinions and who knows improvements that can save her. The subject is not bad.
– Maniero
I agree with the closing, because all the issues discussed are much broader than the premises that the author put. They were cited as references a half dozen web frameworks that are fashionable, but are far from representing everything that encompasses front-end and UI (I would even say that some are bad references). It would be better to edit or redo the question by dealing point by point and choosing the specific environment of each case (or group of familiar environments). In fact, I would say that the best front end experiences for the web (which are already very restricted) do not use any of this there.
– Bacco